Re: [openstack-dev] [all][releases] upcoming library releases to unfreeze requirements in master
Robert Collins wrote: > Endish of my workday, but https://review.openstack.org/#/c/176113/ has > some promise. It doesn't install the 'right' versions- thats something > we're going to have to circle back on, but it does run the tests > successfully, which should unwedge us and let us take a little more > time over the what-gets-installed issue. > > I believe Sean was proposing to disable grenade temporarily. Or we could ninja-merge it to at least unblock stable/kilo and master. -- Thierry Carrez (ttx) __ 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] [all][releases] upcoming library releases to unfreeze requirements in master
On 22 April 2015 at 08:53, Matt Riedemann wrote: > > > On 4/21/2015 2:44 PM, Doug Hellmann wrote: >> >> Excerpts from Doug Hellmann's message of 2015-04-21 13:11:09 -0400: >>> >>> I'm working on releasing a *bunch* of libraries, including clients, from >>> their master branches so we can thaw the requirements list for the >>> liberty cycle. As with any big operation, this may be disruptive. I >>> apologize in advance if it is, but we cannot thaw the requirements >>> without making the releases so we need them all. >>> >>> Here's the full list, in the form of the release script I am running, >>> in case you start seeing issues and want to check if you were >>> affected: >> >> >> OK, this is all done. I have verified that all of the libraries are on >> PyPI and I have sent the release notes (sometimes several copies, at no >> extra charge to you -- seriously, sorry about the noise). >> >> Doug >> >> __ >> 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 >> > > And the gate is wedged. :) > > https://bugs.launchpad.net/openstack-gate/+bug/1446847 Endish of my workday, but https://review.openstack.org/#/c/176113/ has some promise. It doesn't install the 'right' versions- thats something we're going to have to circle back on, but it does run the tests successfully, which should unwedge us and let us take a little more time over the what-gets-installed issue. I believe Sean was proposing to disable grenade temporarily. -Rob -- Robert Collins Distinguished Technologist HP Converged Cloud __ 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] [all][releases] upcoming library releases to unfreeze requirements in master
On Tue, Apr 21, 2015 at 4:35 PM, Joe Gordon wrote: > > > On Tue, Apr 21, 2015 at 1:53 PM, Matt Riedemann < > mrie...@linux.vnet.ibm.com> wrote: > >> >> >> On 4/21/2015 2:44 PM, Doug Hellmann wrote: >> >>> Excerpts from Doug Hellmann's message of 2015-04-21 13:11:09 -0400: >>> I'm working on releasing a *bunch* of libraries, including clients, from their master branches so we can thaw the requirements list for the liberty cycle. As with any big operation, this may be disruptive. I apologize in advance if it is, but we cannot thaw the requirements without making the releases so we need them all. Here's the full list, in the form of the release script I am running, in case you start seeing issues and want to check if you were affected: >>> >>> OK, this is all done. I have verified that all of the libraries are on >>> PyPI and I have sent the release notes (sometimes several copies, at no >>> extra charge to you -- seriously, sorry about the noise). >>> >>> Doug >>> >>> >>> __ >>> 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 >>> >>> >> And the gate is wedged. :) >> >> https://bugs.launchpad.net/openstack-gate/+bug/1446847 >> >> > Double wedged: > > https://bugs.launchpad.net/openstack-gate/+bug/1446882 > > Fixed, now we are back to being are just wedged once. > -- >> >> Thanks, >> >> Matt Riedemann >> >> >> >> __ >> 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] [all][releases] upcoming library releases to unfreeze requirements in master
On Tue, Apr 21, 2015 at 1:53 PM, Matt Riedemann wrote: > > > On 4/21/2015 2:44 PM, Doug Hellmann wrote: > >> Excerpts from Doug Hellmann's message of 2015-04-21 13:11:09 -0400: >> >>> I'm working on releasing a *bunch* of libraries, including clients, from >>> their master branches so we can thaw the requirements list for the >>> liberty cycle. As with any big operation, this may be disruptive. I >>> apologize in advance if it is, but we cannot thaw the requirements >>> without making the releases so we need them all. >>> >>> Here's the full list, in the form of the release script I am running, >>> in case you start seeing issues and want to check if you were >>> affected: >>> >> >> OK, this is all done. I have verified that all of the libraries are on >> PyPI and I have sent the release notes (sometimes several copies, at no >> extra charge to you -- seriously, sorry about the noise). >> >> Doug >> >> __ >> 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 >> >> > And the gate is wedged. :) > > https://bugs.launchpad.net/openstack-gate/+bug/1446847 > > Double wedged: https://bugs.launchpad.net/openstack-gate/+bug/1446882 > -- > > Thanks, > > Matt Riedemann > > > > __ > 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] [all][releases] upcoming library releases to unfreeze requirements in master
On 4/21/2015 2:44 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2015-04-21 13:11:09 -0400: I'm working on releasing a *bunch* of libraries, including clients, from their master branches so we can thaw the requirements list for the liberty cycle. As with any big operation, this may be disruptive. I apologize in advance if it is, but we cannot thaw the requirements without making the releases so we need them all. Here's the full list, in the form of the release script I am running, in case you start seeing issues and want to check if you were affected: OK, this is all done. I have verified that all of the libraries are on PyPI and I have sent the release notes (sometimes several copies, at no extra charge to you -- seriously, sorry about the noise). Doug __ 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 And the gate is wedged. :) https://bugs.launchpad.net/openstack-gate/+bug/1446847 -- Thanks, Matt Riedemann __ 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] [all][releases] upcoming library releases to unfreeze requirements in master
Excerpts from Kevin L. Mitchell's message of 2015-04-21 15:22:29 -0500: > On Tue, 2015-04-21 at 15:44 -0400, Doug Hellmann wrote: > > OK, this is all done. I have verified that all of the libraries are on > > PyPI and I have sent the release notes (sometimes several copies, at no > > extra charge to you -- seriously, sorry about the noise). > > Just out of curiosity, how many entries are in whatever array from which > the script selects randomly? That's the best part of the release > script, IMO :) The release_notes.py script [1] is part of the release-tools repo. If you have emotions to add to the list, please do! Doug [1] http://git.openstack.org/cgit/openstack-infra/release-tools/tree/release_notes.py#n29 __ 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] [all][releases] upcoming library releases to unfreeze requirements in master
On Tue, 2015-04-21 at 15:44 -0400, Doug Hellmann wrote: > OK, this is all done. I have verified that all of the libraries are on > PyPI and I have sent the release notes (sometimes several copies, at no > extra charge to you -- seriously, sorry about the noise). Just out of curiosity, how many entries are in whatever array from which the script selects randomly? That's the best part of the release script, IMO :) -- Kevin L. Mitchell Rackspace __ 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] [all][releases] upcoming library releases to unfreeze requirements in master
Excerpts from Doug Hellmann's message of 2015-04-21 13:11:09 -0400: > I'm working on releasing a *bunch* of libraries, including clients, from > their master branches so we can thaw the requirements list for the > liberty cycle. As with any big operation, this may be disruptive. I > apologize in advance if it is, but we cannot thaw the requirements > without making the releases so we need them all. > > Here's the full list, in the form of the release script I am running, > in case you start seeing issues and want to check if you were > affected: OK, this is all done. I have verified that all of the libraries are on PyPI and I have sent the release notes (sometimes several copies, at no extra charge to you -- seriously, sorry about the noise). Doug __ 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] [all][releases] upcoming library releases to unfreeze requirements in master
I'm working on releasing a *bunch* of libraries, including clients, from their master branches so we can thaw the requirements list for the liberty cycle. As with any big operation, this may be disruptive. I apologize in advance if it is, but we cannot thaw the requirements without making the releases so we need them all. Here's the full list, in the form of the release script I am running, in case you start seeing issues and want to check if you were affected: ./release_library.sh liberty 0.4.0 HEAD debtcollector ./release_library.sh liberty 1.9.0 HEAD oslo.concurrency ./release_library.sh liberty 1.11.0 HEAD oslo.config ./release_library.sh liberty 0.3.0 HEAD oslo.context ./release_library.sh liberty 1.9.0 HEAD oslo.db ./release_library.sh liberty 1.6.0 HEAD oslo.i18n ./release_library.sh liberty 1.1.0 HEAD oslo.log ./release_library.sh liberty 1.10.0 HEAD oslo.messaging ./release_library.sh liberty 1.1.0 HEAD oslo.middleware ./release_library.sh liberty 0.4.0 HEAD oslo.policy ./release_library.sh liberty 1.7.0 HEAD oslo.rootwrap ./release_library.sh liberty 1.5.0 HEAD oslo.serialization ./release_library.sh liberty 1.6.0 HEAD oslotest ./release_library.sh liberty 1.5.0 HEAD oslo.utils ./release_library.sh liberty 0.2.0 HEAD oslo.versionedobjects ./release_library.sh liberty 0.12.0 HEAD oslo.vmware ./release_library.sh liberty 1.4.0 HEAD python-stevedore ./release_library.sh liberty 0.15.0 HEAD python-tooz ./release_library.sh liberty 1.11.0 HEAD python-cliff ./release_library.sh liberty 0.9.0 HEAD taskflow ./release_library.sh liberty 1.3.0 HEAD django_openstack_auth # (no lp project) ./release_library.sh liberty 0.9.0 HEAD pycadf ./release_library.sh liberty 1.6.0 HEAD keystonemiddleware ./release_library.sh liberty 3.1.0 HEAD python-barbicanclient ./release_library.sh liberty 1.2.0 HEAD python-ceilometerclient ./release_library.sh liberty 1.2.0 HEAD python-designateclient ./release_library.sh liberty 0.18.0 HEAD python-glanceclient ./release_library.sh liberty 0.5.0 HEAD python-heatclient ./release_library.sh liberty 0.6.0 HEAD python-ironicclient ./release_library.sh liberty 1.4.0 HEAD python-keystoneclient ./release_library.sh liberty 0.2.0 HEAD python-keystoneclient-kerberos ./release_library.sh liberty 0.1.0 HEAD python-magnumclient ./release_library.sh liberty 1.1.0 HEAD python-manilaclient ./release_library.sh liberty 2.24.0 HEAD python-novaclient ./release_library.sh liberty 1.1.0 HEAD python-openstackclient ./release_library.sh liberty 0.9.0 HEAD python-saharaclient ./release_library.sh liberty 1.1.0 HEAD python-troveclient ./release_library.sh liberty 1.2.0 HEAD python-cinderclient ./release_library.sh liberty 2.5.0 HEAD python-neutronclient # Skipping unreleased projects #./release_library.sh liberty HEAD python-keystoneclient-saml2 #./release_library.sh liberty HEAD python-kiteclient # Skipping unused projects #./release_library.sh liberty 0.2.0 HEAD python-zaqarclient # Skipping projects without caps currently #./release_library.sh liberty 0.5.0 HEAD glance_store (possibly not capped) #./release_library.sh liberty 0.2.0 HEAD ceilometermiddleware (possibly not capped) __ 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
