Re: [openstack-dev] [requirements][all] Freeze starting soon!

On Thu, Jul 27, 2017 at 04:06:09PM +1000, Tony Breeds wrote: > Hi All, > As most of you working on milestone based projects know we're rigth > at the end of the freeze week. This means that at ~UTC Sat 29th > requirements will also freeze. > > global-requirements will be pretty hard

[openstack-dev] Deadline extended for Community Voting

Hi all - Just a quick note that we are extending the deadline for Community Voting due to some early issues we had with the voting system. The deadline is now Thursday, August 03 at 23:59 PM PDT / Friday, August 4 at 6:59 AM UTC. Thank you, Jimmy

Re: [openstack-dev] [all][ptl][stable][release] stable/pike branches created for most libraries

On 07/28/2017 11:13 PM, Doug Hellmann wrote: As Thierry mentioned in his countdown email today, the release team has now created the stable branches for most deliverables with type "library". We have 3 exceptions: 1. python-neutronclient had a late release, so I will be branching it

Re: [openstack-dev] [openstack-doc] Attending PTG?

Alex, I will be there as well and would like to help out! Jay On 7/21/2017 8:41 AM, Alexandra Settle wrote: Hey everyone, Put your hand in the air* if you’re attending the PTG! Myself and the potential PTL will need to start planning shortly, and it would be good to get an idea of

Re: [openstack-dev] [Cinder] Not not running for PTL

Sean, Thank you for all you have done for the project over the last 4 cycles. Anyone who may step up to take your place will have big shoes to fill! Jay On 7/21/2017 6:05 AM, Sean McGinnis wrote: Hey everyone, So this isn't an "I'm stepping down at the end of this cycle" message, but it

Re: [openstack-dev] [release] nominating Sean McGinnis for releases-core

I too am not on the core team but know that Sean will be an asset in this role! +1 On 7/27/2017 10:14 AM, Doug Hellmann wrote: Sean has been increasingly active with the release team this cycle, and wants to contribute. I think we should go ahead and add him to the releases-core group.

Re: [openstack-dev] [docs][release][stable][ptl][infra] Strategic discussion regarding the future of documentation for EOL releases

+2 I am in support of this approach. It is clear that people are still looking for content from older releases long after it has been released but making it clearer that it is an EOL release is an improvement. Jay On 7/28/2017 4:38 AM, Thierry Carrez wrote: Andreas Jaeger wrote: On

Re: [openstack-dev] [release]need help for python-tricircleclient

Hi Joe, You can ping folks on -infra channel on monday to remove the old branch and then we can merge the referenced review to create a fresh one. Thanks, Dims On Sat, Jul 29, 2017 at 2:22 AM, joehuang wrote: > Hello, > > The patch [1] is to add a tag for

[openstack-dev] [tc][dev][trove] Request to consider applying the status:maintenance-mode tag to the Trove project for the Queens cycle

TC, Trove folks, I've submitted [1] a request to the TC to consider applying the status:maintenance-mode tag to the Trove project for the Queens cycle. If you would like to comment on this, I suggest that you do it on the review rather than this email thread. Thanks -amrith [1]

Re: [openstack-dev] [all][ptl][stable][release] stable/pike branches created for most libraries

Thanks for the reminder, I saw related patches showed up in the Gerrit, will ensure them pass validation jobs. 2017-07-29 5:13 GMT+08:00 Doug Hellmann : > As Thierry mentioned in his countdown email today, the release team has > now created the stable branches for most

[openstack-dev] [release]need help for python-tricircleclient

Hello, The patch [1] is to add a tag for python-tricircleclient after new features were added to it since last release. But unfortunately, a branch called "stable/pike" was there in Apr., and lead to the patch can not pass the gate test. "deliverables/pike/python-tricircleclient.yaml: