[openstack-dev] [Fuel] 7.0 Release - Hard Code Freeze in action

[Eugene Bogdanov]

Hello everyone,

Please be informed that Hard Code Freeze for Fuel 7.0 Release is 
officially in action and the following changes have been applied:


1. Stable/7.0 branch was created for the following repos:

fuel-main
fuel-library
fuel-web
fuel-ostf
fuel-astute
fuel-qa
python-fuelclient
fuel-agent
fuel-nailgun-agent
fuel-mirror

2. Development Focus in LP is now changed to 8.0.
3. 7.0 builds are now switched to stable/7.0 branch and new Jenkins jobs 
are created to make builds from master (8.0) [1]. Note that 8.0 builds 
are based on Liberty release and therefore are highly unstable because 
Liberty packaging is currently in progress.


Bug reporters, please ensure you target both master and 7.0 (stable/7.0) 
milestones since now when reporting bugs. Also, please remember that all 
fixes for stable/7.0 branch should first be applied to master (8.0) and 
then cherry-picked to stable/7.0. As always, please ensure that you do 
NOT merge changes to stable branch first. It always has to be a backport 
with the same Change-ID. Please see more on this at [2].


--
EugeneB

[1] https://ci.fuel-infra.org/view/ISO/
[2] 
https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Backport_bugfixes_to_stable_release_series
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] 7.0 Soft Code Freeze in action

[Eugene Bogdanov]

Hello everyone,

I'd like to inform you that Soft Code Freeze[1] for 7.0 release is now 
officially effective. Since now on we stop accepting fixes for Medium 
priority bugs and focus on Critical and High priority bugs. There are 
plenty of them now, we need your help with fixing them so we approach 
Hard Code Freeze in good shape.


With Soft Code Freeze effective, we still have 7.0 blueprints[2] that 
are not implemented. Feature Leads, Component leads and Core Reviewers - 
please help with sorting this out:


1. Please ensure that status of your blueprints is up to date
2. Those blueprints that are not implementedshould be moved to the next
   milestone.
3. If a blueprint is obsolete, the right update is to set definition to
   "Obsolete" with milestone target "nothing selected".

Thank you for your continued contributions.

--
EugeneB

[1] Soft Code Freeze definition: 
https://wiki.openstack.org/wiki/Fuel/Soft_Code_Freeze

[2] https://blueprints.launchpad.net/fuel/7.0.x

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] [upgrade] Cluster Upgrade - FFE status

[Eugene Bogdanov]

Oleg, thanks for the provided information. As discussed verbally, most 
core reviewers are now busy with fixing critical bugs, so you might get 
delayed responses. Keeping in mind, let's target Wednesday, Aug 5 as the 
last deadline. With that said, let's minimize review iterations so core 
reviewers avoid unnecessary focus switch.


--
EugeneB




Oleg Gelbukh 
31 июля 2015 г., 23:00
Team,

I'd like to inform you about status of FF Exception for Cluster 
Upgrade feature.


The due date for the exception was Jul 30th. We had 4 patches to merge 
in the beginning of the work.


During review it was decided that changes to the core of Nailgun 
should be split into separate CR, making it 5 patches. In a course of 
development we also hit a glitch in deep layers of networking modules 
of Nailgun [1]. This slowed down the development and review process, 
and as a result we only merged 1 patch out of 5 by the due date of the 
FFE.


I would like to ask for 4 more days of FFE, which effectively will 
move the due date to Aug 3rd.


[1] https://bugs.launchpad.net/fuel/+bug/1480228

--
Best regards,
Oleg Gelbukh
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] FF Exception for LP-1464656 fix (update ceph PG calculation algorithm)

[Eugene Bogdanov]

Good, thanks everyone for your feedback. Konstantin, let's do as 
suggested - merge pb_num calculation as a bugfix and postpone UI part 
for next release. Indeed, we don't need FF exception here.


--
EugeneB




Vitaly Kramskikh 
27 июля 2015 г., 13:57
+1 to Stanislav's proposal.




--
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Stanislav Makar 
27 июля 2015 г., 3:05

Hello
I went through LP-1464656 and I see that it covers two things:
1. Bad pg num calculation algorithm.
2. Add the possibility to set pg num via GUI.

First is the most important and a BUG by itself, second is nice to 
have feature and no more.

Hence we should split it into a bug and a feature.

As the main part is a bug it does not impact FF at all.

My +1 to close bad pg num calculation algorithm as a bug and postpone 
specifying pg_num via GUI to the next release.


/All the best
Stanislav Makar

+1 for FFE
Given how borken pg_num calculations are now, this is essential to the 
ceph story and there is no point in testing ceph at scale with out it.


The only work-around for not having this is to delete all of the pools 
by hand after deployment and calculate the values by hand, and 
re-create the pools by hand. The story from that alone makes it high 
on the UX scale, which means we might as well fix it as a bug.


The scope of impact is limited to only ceph, the testing plan needs 
more detail, and we are still comming to turns with some of the data 
format to process between nailgun calculating and puppet consuming.


We would need about 1.2 week to get these landed.

--

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 


http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Andrew Woodward 
25 июля 2015 г., 1:58
+1 for FFE
Given how borken pg_num calculations are now, this is essential to the 
ceph story and there is no point in testing ceph at scale with out it.


The only work-around for not having this is to delete all of the pools 
by hand after deployment and calculate the values by hand, and 
re-create the pools by hand. The story from that alone makes it high 
on the UX scale, which means we might as well fix it as a bug.


The scope of impact is limited to only ceph, the testing plan needs 
more detail, and we are still comming to turns with some of the data 
format to process between nailgun calculating and puppet consuming.


We would need about 1.2 week to get these landed.

--

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Konstantin Danilov 
24 июля 2015 г., 13:46
Team,

I would like to request an exception from the Feature Freeze for [1]
fix. It requires changes in
fuel-web [2], fuel-library [3] and in UI. [2] and [3] are already
tested, I'm fixing UT now.
BP - [4]

Code has backward-compatibility mode. I need one more week to finish 
it. Also
I'm asking someone to be an assigned code-reviewer for this ticket to 
speed-up

review process.

Thanks

[1] https://bugs.launchpad.net/fuel/+bug/1464656
[2] https://review.openstack.org/#/c/204814
[3] https://review.openstack.org/#/c/204811
[4] https://review.openstack.org/#/c/203062



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [fuel] FF Exception for LP-1464656 fix (update ceph PG calculation algorithm)

[Eugene Bogdanov]

Good, thanks everyone for your feedback. As suggested, let's merge 
pb_num calculation as a bugfix (no exception needed). With regards to UI 
part, I do agree that it's just nice to have feature and I don't see the 
review with GUI part amongst of those nominated for exception. So - 
let's put it to the next release.


--
EugeneB


Vitaly Kramskikh 
27 июля 2015 г., 13:57
+1 to Stanislav's proposal.




--
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Stanislav Makar 
27 июля 2015 г., 3:05

Hello
I went through LP-1464656 and I see that it covers two things:
1. Bad pg num calculation algorithm.
2. Add the possibility to set pg num via GUI.

First is the most important and a BUG by itself, second is nice to 
have feature and no more.

Hence we should split it into a bug and a feature.

As the main part is a bug it does not impact FF at all.

My +1 to close bad pg num calculation algorithm as a bug and postpone 
specifying pg_num via GUI to the next release.


/All the best
Stanislav Makar

+1 for FFE
Given how borken pg_num calculations are now, this is essential to the 
ceph story and there is no point in testing ceph at scale with out it.


The only work-around for not having this is to delete all of the pools 
by hand after deployment and calculate the values by hand, and 
re-create the pools by hand. The story from that alone makes it high 
on the UX scale, which means we might as well fix it as a bug.


The scope of impact is limited to only ceph, the testing plan needs 
more detail, and we are still comming to turns with some of the data 
format to process between nailgun calculating and puppet consuming.


We would need about 1.2 week to get these landed.

--

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 


http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Andrew Woodward 
25 июля 2015 г., 1:58
+1 for FFE
Given how borken pg_num calculations are now, this is essential to the 
ceph story and there is no point in testing ceph at scale with out it.


The only work-around for not having this is to delete all of the pools 
by hand after deployment and calculate the values by hand, and 
re-create the pools by hand. The story from that alone makes it high 
on the UX scale, which means we might as well fix it as a bug.


The scope of impact is limited to only ceph, the testing plan needs 
more detail, and we are still comming to turns with some of the data 
format to process between nailgun calculating and puppet consuming.


We would need about 1.2 week to get these landed.

--

--

Andrew Woodward

Mirantis

Fuel Community Ambassador

Ceph Community

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Konstantin Danilov 
24 июля 2015 г., 13:46
Team,

I would like to request an exception from the Feature Freeze for [1]
fix. It requires changes in
fuel-web [2], fuel-library [3] and in UI. [2] and [3] are already
tested, I'm fixing UT now.
BP - [4]

Code has backward-compatibility mode. I need one more week to finish 
it. Also
I'm asking someone to be an assigned code-reviewer for this ticket to 
speed-up

review process.

Thanks

[1] https://bugs.launchpad.net/fuel/+bug/1464656
[2] https://review.openstack.org/#/c/204814
[3] https://review.openstack.org/#/c/204811
[4] https://review.openstack.org/#/c/203062




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] 7.0 Release - Feature Freeze in action

[Eugene Bogdanov]

Hello everyone,

Please be informed that we have officially entered Feature Freeze state 
for Fuel 7.0 Release. This means that since now on we focus on bugfixing 
and stop accepting new code except bugfix commits. If you believe that 
the code for your feature still needs to be merged as an exception, 
please file an exception request as described in [1].


3 Feature Freeze Exception requests have already been filed [2]. We're 
working closely with Feature Leads and Core Reviewers to assess risks 
and additional time estimations. We expect to take decisions on all 3 
cases by tomorrow EOD Pacific Time and communicate them in respective 
threads.


Thanks everyone for your contributions and collaborative efforts. Let's 
keep up good work.


--
EugeneB

[1] https://wiki.openstack.org/wiki/FeatureFreeze

[2] Exception requests:

#1: Environment Upgrade extensions for Nailgun API:
https://review.openstack.org/#/c/192551/

#2: CLI changes of working with custom node labels:
_https://review.openstack.org/#/c/204524/_

#3: Fernet Tokens support:
https://review.openstack.org/#/c/201029/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] Fuel for Openstack 6.1 released

[Eugene Bogdanov]

Hello everyone,

I am glad to inform you that Fuel for Openstack 6.1 is out now. Feel 
free to download the new release from https://www.fuel-infra.org.


Thanks to all contributors for making this release happen.

--
EugeneB


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] MOS 6.1 Release - Hard Code Freeze in action

[Eugene Bogdanov]

Hello everyone,

Please be informed that Hard Code Freeze for MOS 6.1 Release is 
officially in action. As mentioned earlier, stable/6.1 branch was 
created for the following repos:


  fuel-astute
  fuel-docs
  fuel-library
  fuel-main
  fuel-ostf
  fuel-qa
  fuel-web

Bug reporters, please do not forget to target both master and 6.1 
(stable/6.1) milestones since now. Also, please remember that all fixes 
for stable/6.1 branch should first be applied to master and then 
cherry-picked to stable/6.1. As always, please ensure that you do NOT 
merge changes to stable branch first. It always has to be a backport 
with the same Change-ID. Please see more on this at [1]


--
EugeneB

[1] 
https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Backport_bugfixes_to_stable_release_series
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] 6.1 RC ready, Hard Code Freeze to be announced on Monday, June 8th

[Eugene Bogdanov]

Good news everyone, our internal tests have completed successfully and 
we now have RC build. Fuel DevOps team members are unavailable during 
the weekend, so we will create stable/6.1 branches for our repos on 
Monday, June 8th. Once created, we will officially declare Hard Code 
Freeze status and share the RC ISO links.


Stay tuned and have a great weekend.

--
EugeneB


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] 6.1 Hard Code Freeze status update June 5th

[Eugene Bogdanov]

Hello everyone,

Unfortunately the recent patch for SWIFT issue [1] broke our staging 
tests last night. The problem is now resolved, new staging tests passed 
successfully. We need ~12 hours more to run the newly built ISO through 
SWARM tests, so we will have the results tomorrow morning MSK. If they 
are good, we'll declare HCF status tonight/early morning Saturday (June 
6th).


We are not sure why this patch passed through our internal control 
systems, we will do thorough root cause analysis early next week.


[1] https://bugs.launchpad.net/fuel/+bug/1462142

--
EugeneB

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] Hard Code Freeze status update - Just 4th 2PM PDT

[Eugene Bogdanov]

Hello everyone,

The Keystone patch passed staging tests, we are now building the ISO 
with this patch and other merged fixes. Test results for this ISO will 
be available tonight/early morning tomorrow PDT. If they are good, this 
will be our RC. So, our plan to declare HCF tomorrow morning/afternoon 
PDT (June 5th) looks realistic.


--
EugeneB



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] Hard Code Freeze status update - Just 3rd 2:30PM PDT

[Eugene Bogdanov]

Hello everyone,

We are still struggling with Keystone bugs [1]. This is the only 
showstopper for HCF. The plan is - we close this out tomorrow, make an 
ISO and put it through smoke testing overnight. If the test results do 
not show regression, we declare HCF on Friday, June 5thwith defining 
this ISO as RC and focus our further efforts on manual acceptance.


[1] Keystone bugs:
https://bugs.launchpad.net/fuel/+bug/1461036 - investigating (marked as 
Incomplete so far)
https://bugs.launchpad.net/fuel/+bug/1458806 - investigating (marked as 
Incomplete so far)
https://bugs.launchpad.net/mos/+bug/1461655 - discovered today, 
investigating.


--
EugeneB








__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] 6.1 Hard Code Freeze - status update June 2nd

[Eugene Bogdanov]

Hello everyone,

We currently see 6 bugs as main HCF dependencies [1]. We'll try to close 
all of them overnight. If we don't succeed, we'll need another day. 
We'll take decision whether we do/do not declare HCF based on the 
results tomorrow morning PDT.


[1] Key HCF dependencies:
https://bugs.launchpad.net/fuel/+bug/1461036 - in progress
https://bugs.launchpad.net/fuel/+bug/1458806 - in progress
https://bugs.launchpad.net/fuel/+bug/1460972 - on review
https://bugs.launchpad.net/fuel/6.1.x/+bug/1458533 - on review
https://bugs.launchpad.net/fuel/+bug/1461206 - discovered just today
https://bugs.launchpad.net/fuel/+bug/1461126 - discovered just today

Automated testing results:
CentOS - 73% pass rate
Ubuntu - 77% pass rate

--
EugeneB

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] Hard Code Freeze status update - Just 1st 8PM PDT

[Eugene Bogdanov]

Hello everyone,

We keep fixing bugs with a decent pace, but we received 2 critical and 
10+ high new bugs from QA today. All manageable, but we need 1 more day 
to close them out and do smoke testing. So, ETA for HardCodeFreeze is 
June 3rd.


Today's stats:

Bugs left:  7 bugs + 17 incomplete.
Automated tests pass rate: 72% for CentoOS, 70% for Ubuntu.

--
EugeneB

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] 6.1 Release - new dates for HCF and GA

[Eugene Bogdanov]

Hello everyone,

We keep putting our best efforts to hit Hard Code Freeze goals. Latest 
test results are 68% pass rate for Ubuntu and 65% for CentOS. Once the 
remaining bugs are closed, we will be able to hit 70% target for sure. 
Based on the feedback from Engineering leads, with current 
incoming/outgoing ratio the chance to close all remaining bugs by Friday 
this week is high and we'll then need a couple of days to settle down 
with Release Candidate. So, we will target June 2nd for Hard Code Freeze.


Our history of releases show that we need 3 additional weeks on average 
to transform Release Candidate to final RTM build, so we'll target GA 
date is June 23rd.


I have updated the schedule with the above dates. Thank you.

--
EugeneB

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] 6.1 HCF delayed, release date to be revised

[Eugene Bogdanov]

Hello everyone,

Our HCF milestone date was on May 12th, but unfortunately the amount of 
bugs at this point still does not meet HCF criteria [1]. Our current 
plan is the following:


1. Close the remaining high and critical bugs that fall to HCF criteria. 
Creating filter for these bugs with Launchpad means is tricky, so I am 
just publishing the list of bugs below [2]
2. Achieve at least 70% of passes in automated tests coverage (current 
numbers are 61% for Ubuntu and 42% for CentOS).


We hope to complete these action items by May 22th.

We will revise GA date estimations once we hit the HCF goals. If the GA 
date is changed, I'll send an update.


I realize that I should have sent this earlier, I apologize for the 
delay with communication.


--
EugeneB

[1] Hard Code Freeze criteria: 
https://wiki.openstack.org/wiki/Fuel/Hard_Code_Freeze


[2] List of bugs left to be fixed (valid on May 20th, more bugs can be 
added later on if discovered).


https://bugs.launchpad.net/fuel/+bug/1439686
https://bugs.launchpad.net/fuel/+bug/1456325
https://bugs.launchpad.net/fuel/+bug/1455048
https://bugs.launchpad.net/fuel/+bug/1454763
https://bugs.launchpad.net/fuel/+bug/1455660
https://bugs.launchpad.net/fuel/+bug/1456191
https://bugs.launchpad.net/fuel/+bug/1443925
https://bugs.launchpad.net/fuel/+bug/1454741
https://bugs.launchpad.net/fuel/+bug/1455390
https://bugs.launchpad.net/fuel/+bug/1455539
https://bugs.launchpad.net/fuel/+bug/1456276
https://bugs.launchpad.net/fuel/+bug/1456587
https://bugs.launchpad.net/fuel/+bug/1456634
https://bugs.launchpad.net/fuel/6.1.x/+bug/1441435
https://bugs.launchpad.net/fuel/+bug/1443913
https://bugs.launchpad.net/fuel/+bug/1455661
https://bugs.launchpad.net/fuel/+bug/1456540
https://bugs.launchpad.net/fuel/+bug/1456630
https://bugs.launchpad.net/fuel/+bug/1456791
https://bugs.launchpad.net/fuel/+bug/1456491
https://bugs.launchpad.net/mos/6.1.x/+bug/1422350
https://bugs.launchpad.net/mos/6.1.x/+bug/1456243
https://bugs.launchpad.net/fuel/+bug/1455513
https://bugs.launchpad.net/fuel/+bug/1455923
https://bugs.launchpad.net/fuel/+bug/1456459
https://bugs.launchpad.net/fuel/+bug/1456605
https://bugs.launchpad.net/fuel/+bug/1456746
https://bugs.launchpad.net/fuel/+bug/1456526
https://bugs.launchpad.net/fuel/+bug/1449977
https://bugs.launchpad.net/fuel/+bug/1456805








__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Fuel] 6.1 SCF declared, new HCF/GA dates are May 12th / May 28th

[Eugene Bogdanov]

Hello everyone,

I'd like to inform you that Soft Code Freeze for 6.1 release is now 
effective. This means that since now on we stop accepting fixes for 
Medium priority bugs and focus solely on Critical and High priority bugs.


As mentioned last week, we need to push Hard Code Freeze and GA 
deadlines. New dates are May 12th and May 28th respectively. 6.1 Release 
Schedule[1] has been updated.


With Soft Code Freeze in action, we still have 6.1 blueprints[1] not 
sorted out properly. Feature Leads, Component leads and Core Reviewers - 
we need your help with sorting this out:


1. Those blueprints that are not implementedshould be moved to the next
   milestone.
2. If a blueprint is obsolete, the right update is to set definition to
   "Obsolete" with milestone target "nothing selected".

Thank you for your continued assistance. Hopefully, this is our last 
shift of 6.1 milestone dates and we'll be able to deliver on May 28th 
with high quality.


--
EugeneB


[1] Fuel 6.1 Release Schedule: 
https://wiki.openstack.org/wiki/Fuel/6.1_Release_Schedule
[2] Fuel 6.1 Milestone blueprint list: 
https://launchpad.net/fuel/+milestone/6.1


Eugene Bogdanov wrote:

Hello everyone,

Upon latest estimations from Feature Leads, we need 1 more week to 
complete FF exceptions and bugfixing so we could match Soft Code 
Freeze milestone criteria[1]. In this case, the new Soft Code Freeze 
date is April 16th. That said, we will continue accepting medium/low 
priority bugfix commits into 6.1 milestone[3] for one more week. I 
have update 6.1 Release Schedule[2] accordingly.


With last 2 shifts of Soft Code Freeze date, there's obviously too 
little time left to prepare for Hard Code Freeze[3] and GA milestones, 
so we'll have to push these a bit as well. New dates are currently 
under discussion and will be communicated early next week.


I'd like to thank everyone for your continued contributions. Let's use 
additional time efficiently and make MOS 6.1 release quality as high 
as we possibly can.


[1] Soft Code Freeze definition: 
https://wiki.openstack.org/wiki/Fuel/Soft_Code_Freeze

[2] Release schedule:
https://wiki.openstack.org/wiki/Fuel/6.1_Release_Schedule
[3] Fuel 6.1 Milestone scope: https://launchpad.net/fuel/+milestone/6.1
[4] Hard Code Freeze definition: 
https://wiki.openstack.org/wiki/Fuel/Hard_Code_Freeze


--
EugeneB

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] 6.1 Soft Code Freeze moved to April 7th

[Eugene Bogdanov]

Hello everyone,

We 
currently 
have 500+ medium priority bugs assigned to 6.1 release. Obviously we 
won't be able to make a big difference within the next 24 hours, so 
let's move the Soft Code Freeze date (last date when medium bug fixes 
are accepted) [1] to April 7th. This will give us some time to apply 
important bug fixes and complete triaging as appropriate. The shift is 
only about Soft Code Freeze (no changes for Hard Code Freeze / GA 
dates). I have updated the release schedule [2] accordingly.


Thank you.

[1] Soft Code Freeze definition: 
https://wiki.openstack.org/wiki/Fuel/Soft_Code_Freeze
[2] Release schedule: 
https://wiki.openstack.org/wiki/Fuel/6.1_Release_Schedule


--
EugeneB


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Fuel 6.1 Feature Freeze in action, further milestones postponed for 2 weeks

[Eugene Bogdanov]

Hi everyone,

As we continue working on Fuel 6.1 release, let me share some updates. I 
do realize I should have shared this earlier, I apologize for the delay 
with this communication. So, here we go:


1. We are officially at Feature Freeze for 6.1.
According to our Release Schedule for 6.1 [1] with quite a bit of 
exceptions [2] we have entered into Feature Freeze [3] state. As usual, 
let me request Feature Leads', Component leads' and core reviewers' help 
with sorting out the blueprints - many have to be properly updated, and 
other (not started/not completed) moved to the next milestone.


2. 6.1 Soft Code Freeze and further milestones are postponed for 2 weeks.
We cannot declare Soft Code Freeze until we are done with all 
exceptions. Based on cumulative Feature Leads' feedback, we'll need 
roughly 2 weeks to deal with all exceptions and perform the necessary 
level of QA, so we have updated the Release Schedule with new dates for 
Soft Code Freeze (March 31st), Hard Code Freeze (April 23rd) and GA 
Release (May 14th).


Another challenge is that we have quite considerable amount of Medium 
Priority bugs. To ensure good quality of this release we also need to 
fix as many Medium Priority bugs before we declare Soft Code Freeze, so 
we greatly appreciate your contributions here.


Thank you very much for your continued contributions, your efforts are 
greatly appreciated.


[1] https://wiki.openstack.org/wiki/Fuel/6.1_Release_Schedule

[2] List of current FF exceptions for 6.1 release:
https://blueprints.launchpad.net/fuel/+spec/plugins-deployment-order
https://blueprints.launchpad.net/fuel/+spec/consume-external-ubuntu
https://blueprints.launchpad.net/fuel/+spec/200-nodes-support
https://blueprints.launchpad.net/fuel/+spec/separate-mos-from-linux
https://blueprints.launchpad.net/murano/+spec/muraniclient-url-download
https://blueprints.launchpad.net/fuel/+spec/fuel-library-modularization
https://blueprints.launchpad.net/fuel/+spec/support-ubuntu-trusty

[3] https://wiki.openstack.org/wiki/FeatureFreeze


--
EugeneB

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev