Re: [openstack-dev] [all][stable][release] 2015.1.2

2015-10-14 10:59 GMT+02:00 Thierry Carrez : > Sean Dague wrote: >> I think that whoever sets the tag should also push those fixes. We had >> some kilo content bogging down the gate today because of this kind of >> failure. Better to time this as close as possible with the

Re: [openstack-dev] [all][stable][release] 2015.1.2

> On 13 Oct 2015, at 21:56, Matt Riedemann wrote: > > > > On 10/13/2015 1:57 PM, Chuck Short wrote: >> Hi >> >> Im just in the last stages of release 2015.1.2. I dont think anything is >> stopping us from opening it up agian. The tabrlls have been created. So >> go

Re: [openstack-dev] [all][stable][release] 2015.1.2

Ihar Hrachyshka wrote: > Chuck, have you forgotten about three more repositories for neutron-*aas? Yeah, if those have fixes they should have been tagged as well. Also we'll want a change to openstack/releases to include 2015.1.2 in release history. -- Thierry Carrez (ttx) signature.asc

Re: [openstack-dev] [all][stable][release] 2015.1.2

Sean Dague wrote: > I think that whoever sets the tag should also push those fixes. We had > some kilo content bogging down the gate today because of this kind of > failure. Better to time this as close as possible with the tag setting. Right. The ideal process is to push the version bump and cut

Re: [openstack-dev] [all][stable][release] 2015.1.2

On Wed, Oct 14, 2015 at 5:01 AM, Thierry Carrez wrote: > Ihar Hrachyshka wrote: > > Chuck, have you forgotten about three more repositories for neutron-*aas? > My apologies they are available now. > > Yeah, if those have fixes they should have been tagged as well. > >

Re: [openstack-dev] [all][stable][release] 2015.1.2

On 10/13/2015 1:57 PM, Chuck Short wrote: Hi Im just in the last stages of release 2015.1.2. I dont think anything is stopping us from opening it up agian. The tabrlls have been created. So go for it. Chuck On Tue, Oct 13, 2015 at 2:46 PM, Matt Riedemann

Re: [openstack-dev] [all][stable][release] 2015.1.2

On 10/13/2015 02:57 PM, Chuck Short wrote: > Hi > > Im just in the last stages of release 2015.1.2. I dont think anything is > stopping us from opening it up agian. The tabrlls have been created. So > go for it. Chuck, I think that whoever sets the tag should also push those fixes. We had some

Re: [openstack-dev] [all][stable][release] 2015.1.2

On 10/13/2015 01:46 PM, Matt Riedemann wrote: > > > On 10/7/2015 7:42 PM, Chuck Short wrote: >> Hi, >> stable/kilo is now frozen. I expect to do a release on Tuesday. If you >> need to include something please let me know. >> >> Thanks >> chuck >> >> >>

Re: [openstack-dev] [all][stable][release] 2015.1.2

Hi Im just in the last stages of release 2015.1.2. I dont think anything is stopping us from opening it up agian. The tabrlls have been created. So go for it. Chuck On Tue, Oct 13, 2015 at 2:46 PM, Matt Riedemann wrote: > > > On 10/7/2015 7:42 PM, Chuck Short

Re: [openstack-dev] [all][stable][release] 2015.1.2

On 10/7/2015 7:42 PM, Chuck Short wrote: Hi, stable/kilo is now frozen. I expect to do a release on Tuesday. If you need to include something please let me know. Thanks chuck __ OpenStack Development Mailing List (not

[openstack-dev] [all][stable][release] 2015.1.2

Hi, stable/kilo is now frozen. I expect to do a release on Tuesday. If you need to include something please let me know. Thanks chuck __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [all][stable][release] 2015.1.2

Hi, I would like to freeze the branches on Wednesday and get a release out early next week. Are we okay with that? Thanks chuck On Wed, Sep 23, 2015 at 8:47 PM, Chuck Short wrote: > Hi, > > We would like to do a stable/kilo branch release, next Thursday. In order >

Re: [openstack-dev] [all][stable][release] 2015.1.2

Chuck Short wrote: > I would like to freeze the branches on Wednesday and get a release out > early next week. Are we okay with that? Next week is Liberty release week so that might be confusing... But if it's the only option, as long as it's *early* next week, I guess that won't hurt. --

Re: [openstack-dev] [all][stable][release] 2015.1.2

On 25/09/15 00:17, Alan Pevec wrote: >> For Horizon, it would make sense to move this a week back. We discovered >> a few issues in Liberty, which are present in current kilo, too. I'd >> love to cherry-pick a few of them to kilo. > > What are LP bug#s ? Are you saying that fixes are still work

Re: [openstack-dev] [all][stable][release] 2015.1.2

> On 25 Sep 2015, at 09:02, Matthias Runge wrote: > > On 25/09/15 00:17, Alan Pevec wrote: >>> For Horizon, it would make sense to move this a week back. We discovered >>> a few issues in Liberty, which are present in current kilo, too. I'd >>> love to cherry-pick a few of

Re: [openstack-dev] [all][stable][release] 2015.1.2

On Wed, Sep 23, 2015 at 08:47:31PM -0400, Chuck Short wrote: > Hi, > > We would like to do a stable/kilo branch release, next Thursday. In order > to do that I would like to freeze the branches on Friday. Cut some test > tarballs on Tuesday and release on Thursday. Does anyone have an opinnon on

Re: [openstack-dev] [all][stable][release] 2015.1.2

On Wed, Sep 23, 2015 at 08:47:31PM -0400, Chuck Short wrote: > Hi, > > We would like to do a stable/kilo branch release, next Thursday. In order > to do that I would like to freeze the branches on Friday. Cut some test > tarballs on Tuesday and release on Thursday. Does anyone have an opinnon on

Re: [openstack-dev] [all][stable][release] 2015.1.2

> For Horizon, it would make sense to move this a week back. We discovered > a few issues in Liberty, which are present in current kilo, too. I'd > love to cherry-pick a few of them to kilo. What are LP bug#s ? Are you saying that fixes are still work in progress on master and not ready for

[openstack-dev] [all][stable][release] 2015.1.2

Hi, We would like to do a stable/kilo branch release, next Thursday. In order to do that I would like to freeze the branches on Friday. Cut some test tarballs on Tuesday and release on Thursday. Does anyone have an opinnon on this? Thanks chuck