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

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-age

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

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 approa

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

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 reviewe

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

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 Stanisl

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

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 t

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

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 excep

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

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-dev] [Fuel] MOS 6.1 Release - Hard Code Freeze in action

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 no

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

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

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

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

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

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/after

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

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 t

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

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.

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

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. A

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

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 incom

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

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 Lau

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

lestone 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 Fr

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

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 with

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

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]