Re: [openstack-dev] [release][ptl] tools for creating new releases
On 08/22/2017 02:34 PM, Doug Hellmann wrote: Excerpts from Dmitry Tantsur's message of 2017-08-22 11:38:10 +0200: On 08/22/2017 11:34 AM, Dmitry Tantsur wrote: On 08/21/2017 09:15 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2017-08-21 11:21:59 -0400: Excerpts from Dmitry Tantsur's message of 2017-08-15 14:11:05 +0200: On 08/08/2017 03:30 PM, Doug Hellmann wrote: We realized recently that we haven't publicized some of the tools in the releases repository very well. One tool that will be useful this week as you prepare your release candidates is the 'new-release' command, which edits a deliverable file to add a new release from HEAD of the given branch, automatically computing the next verison number based on the inputs. Use the ``venv`` tox environment to run the tool, like this: $ tox -e venv -- new-release SERIES DELIVERABLE TYPE The SERIES value should be the release series, such as "pike". The DELIVERABLE value should be the deliverable name, such as "oslo.config" or "cinder". The TYPE value should be one of "bugfix", "feature", "major", "milestone", or "rc". If the most recent release of cinder during the pike series is 11.0.0.0b3 then running: $ tox -e venv -- new-release pike cinder rc On systems with Python 3 by default this fails on installing lazr.restfulclient. I think we should add basepython = python2 for now. I wonder if you have an old copy of the releases repo. In master we explicitly set basepython to python3 and lazr.restfulclient is no longer a dependency. Updated to latest HEAD, removed *.pyc files and .tox. Still getting: Obtaining file:///home/dtantsur/Projects/releases Requirement already up-to-date: pbr>=1.6 in ./.tox/list-changes/lib/python3.6/site-packages (from releases==0.0.1.dev3083) Collecting lazr.restfulclient==0.13.1 (from releases==0.0.1.dev3083) Using cached lazr.restfulclient-0.13.1.tar.gz Complete output from command python setup.py egg_info: Traceback (most recent call last): File "", line 1, in File "/tmp/pip-build-hhi229rh/lazr.restfulclient/setup.py", line 19, in import ez_setup File "/tmp/pip-build-hhi229rh/lazr.restfulclient/ez_setup.py", line 98 except pkg_resources.VersionConflict, e: ^ SyntaxError: invalid syntax I cannot find where this dependency comes from, still investigating. And here is what helped: rm -rf *.egg-info/ I suspect it was coming from stale directory releases.egg-info (currently we have openstack_releases.egg-info instead). I'm not sure why it was picked.. Yes, that's odd, but I'm glad you found the problem. I see you're running with python 3.6. I've only tested with 3.5 so far, so I would appreciate bug reports or patches if you find issues. So far so good. I haven't had any problems with doing Pike releases on it. 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 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] [release][ptl] tools for creating new releases
Excerpts from Dmitry Tantsur's message of 2017-08-22 11:38:10 +0200: > On 08/22/2017 11:34 AM, Dmitry Tantsur wrote: > > On 08/21/2017 09:15 PM, Doug Hellmann wrote: > >> Excerpts from Doug Hellmann's message of 2017-08-21 11:21:59 -0400: > >>> Excerpts from Dmitry Tantsur's message of 2017-08-15 14:11:05 +0200: > On 08/08/2017 03:30 PM, Doug Hellmann wrote: > > We realized recently that we haven't publicized some of the tools > > in the releases repository very well. One tool that will be useful > > this week as you prepare your release candidates is the 'new-release' > > command, which edits a deliverable file to add a new release from > > HEAD of the given branch, automatically computing the next verison > > number based on the inputs. > > > > Use the ``venv`` tox environment to run the tool, like this: > > > > $ tox -e venv -- new-release SERIES DELIVERABLE TYPE > > > > The SERIES value should be the release series, such as "pike". > > > > The DELIVERABLE value should be the deliverable name, such as > > "oslo.config" or "cinder". > > > > The TYPE value should be one of "bugfix", "feature", "major", > > "milestone", or "rc". > > > > If the most recent release of cinder during the pike series is > > 11.0.0.0b3 then running: > > > > $ tox -e venv -- new-release pike cinder rc > > On systems with Python 3 by default this fails on installing > lazr.restfulclient. > I think we should add > > basepython = python2 > > for now. > >> > >> I wonder if you have an old copy of the releases repo. In master we > >> explicitly set basepython to python3 and lazr.restfulclient is no longer > >> a dependency. > > > > Updated to latest HEAD, removed *.pyc files and .tox. Still getting: > > > > Obtaining file:///home/dtantsur/Projects/releases > > Requirement already up-to-date: pbr>=1.6 in > > ./.tox/list-changes/lib/python3.6/site-packages (from > > releases==0.0.1.dev3083) > > Collecting lazr.restfulclient==0.13.1 (from releases==0.0.1.dev3083) > >Using cached lazr.restfulclient-0.13.1.tar.gz > > Complete output from command python setup.py egg_info: > > Traceback (most recent call last): > >File "", line 1, in > >File "/tmp/pip-build-hhi229rh/lazr.restfulclient/setup.py", line 19, > > in > > > > import ez_setup > >File "/tmp/pip-build-hhi229rh/lazr.restfulclient/ez_setup.py", line > > 98 > > except pkg_resources.VersionConflict, e: > > ^ > > SyntaxError: invalid syntax > > > > I cannot find where this dependency comes from, still investigating. > > And here is what helped: rm -rf *.egg-info/ > > I suspect it was coming from stale directory releases.egg-info (currently we > have openstack_releases.egg-info instead). I'm not sure why it was picked.. Yes, that's odd, but I'm glad you found the problem. I see you're running with python 3.6. I've only tested with 3.5 so far, so I would appreciate bug reports or patches if you find issues. 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
Re: [openstack-dev] [release][ptl] tools for creating new releases
On 08/22/2017 11:34 AM, Dmitry Tantsur wrote: On 08/21/2017 09:15 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2017-08-21 11:21:59 -0400: Excerpts from Dmitry Tantsur's message of 2017-08-15 14:11:05 +0200: On 08/08/2017 03:30 PM, Doug Hellmann wrote: We realized recently that we haven't publicized some of the tools in the releases repository very well. One tool that will be useful this week as you prepare your release candidates is the 'new-release' command, which edits a deliverable file to add a new release from HEAD of the given branch, automatically computing the next verison number based on the inputs. Use the ``venv`` tox environment to run the tool, like this: $ tox -e venv -- new-release SERIES DELIVERABLE TYPE The SERIES value should be the release series, such as "pike". The DELIVERABLE value should be the deliverable name, such as "oslo.config" or "cinder". The TYPE value should be one of "bugfix", "feature", "major", "milestone", or "rc". If the most recent release of cinder during the pike series is 11.0.0.0b3 then running: $ tox -e venv -- new-release pike cinder rc On systems with Python 3 by default this fails on installing lazr.restfulclient. I think we should add basepython = python2 for now. I wonder if you have an old copy of the releases repo. In master we explicitly set basepython to python3 and lazr.restfulclient is no longer a dependency. Updated to latest HEAD, removed *.pyc files and .tox. Still getting: Obtaining file:///home/dtantsur/Projects/releases Requirement already up-to-date: pbr>=1.6 in ./.tox/list-changes/lib/python3.6/site-packages (from releases==0.0.1.dev3083) Collecting lazr.restfulclient==0.13.1 (from releases==0.0.1.dev3083) Using cached lazr.restfulclient-0.13.1.tar.gz Complete output from command python setup.py egg_info: Traceback (most recent call last): File "", line 1, in File "/tmp/pip-build-hhi229rh/lazr.restfulclient/setup.py", line 19, in import ez_setup File "/tmp/pip-build-hhi229rh/lazr.restfulclient/ez_setup.py", line 98 except pkg_resources.VersionConflict, e: ^ SyntaxError: invalid syntax I cannot find where this dependency comes from, still investigating. And here is what helped: rm -rf *.egg-info/ I suspect it was coming from stale directory releases.egg-info (currently we have openstack_releases.egg-info instead). I'm not sure why it was picked.. 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 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] [release][ptl] tools for creating new releases
On 08/21/2017 09:15 PM, Doug Hellmann wrote: Excerpts from Doug Hellmann's message of 2017-08-21 11:21:59 -0400: Excerpts from Dmitry Tantsur's message of 2017-08-15 14:11:05 +0200: On 08/08/2017 03:30 PM, Doug Hellmann wrote: We realized recently that we haven't publicized some of the tools in the releases repository very well. One tool that will be useful this week as you prepare your release candidates is the 'new-release' command, which edits a deliverable file to add a new release from HEAD of the given branch, automatically computing the next verison number based on the inputs. Use the ``venv`` tox environment to run the tool, like this: $ tox -e venv -- new-release SERIES DELIVERABLE TYPE The SERIES value should be the release series, such as "pike". The DELIVERABLE value should be the deliverable name, such as "oslo.config" or "cinder". The TYPE value should be one of "bugfix", "feature", "major", "milestone", or "rc". If the most recent release of cinder during the pike series is 11.0.0.0b3 then running: $ tox -e venv -- new-release pike cinder rc On systems with Python 3 by default this fails on installing lazr.restfulclient. I think we should add basepython = python2 for now. I wonder if you have an old copy of the releases repo. In master we explicitly set basepython to python3 and lazr.restfulclient is no longer a dependency. Updated to latest HEAD, removed *.pyc files and .tox. Still getting: Obtaining file:///home/dtantsur/Projects/releases Requirement already up-to-date: pbr>=1.6 in ./.tox/list-changes/lib/python3.6/site-packages (from releases==0.0.1.dev3083) Collecting lazr.restfulclient==0.13.1 (from releases==0.0.1.dev3083) Using cached lazr.restfulclient-0.13.1.tar.gz Complete output from command python setup.py egg_info: Traceback (most recent call last): File "", line 1, in File "/tmp/pip-build-hhi229rh/lazr.restfulclient/setup.py", line 19, in import ez_setup File "/tmp/pip-build-hhi229rh/lazr.restfulclient/ez_setup.py", line 98 except pkg_resources.VersionConflict, e: ^ SyntaxError: invalid syntax I cannot find where this dependency comes from, still investigating. 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 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] [release][ptl] tools for creating new releases
Excerpts from Doug Hellmann's message of 2017-08-21 11:21:59 -0400: > Excerpts from Dmitry Tantsur's message of 2017-08-15 14:11:05 +0200: > > On 08/08/2017 03:30 PM, Doug Hellmann wrote: > > > We realized recently that we haven't publicized some of the tools > > > in the releases repository very well. One tool that will be useful > > > this week as you prepare your release candidates is the 'new-release' > > > command, which edits a deliverable file to add a new release from > > > HEAD of the given branch, automatically computing the next verison > > > number based on the inputs. > > > > > > Use the ``venv`` tox environment to run the tool, like this: > > > > > > $ tox -e venv -- new-release SERIES DELIVERABLE TYPE > > > > > > The SERIES value should be the release series, such as "pike". > > > > > > The DELIVERABLE value should be the deliverable name, such as > > > "oslo.config" or "cinder". > > > > > > The TYPE value should be one of "bugfix", "feature", "major", > > > "milestone", or "rc". > > > > > > If the most recent release of cinder during the pike series is > > > 11.0.0.0b3 then running: > > > > > > $ tox -e venv -- new-release pike cinder rc > > > > On systems with Python 3 by default this fails on installing > > lazr.restfulclient. > > I think we should add > > > > basepython = python2 > > > > for now. I wonder if you have an old copy of the releases repo. In master we explicitly set basepython to python3 and lazr.restfulclient is no longer a dependency. 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
Re: [openstack-dev] [release][ptl] tools for creating new releases
Excerpts from Dmitry Tantsur's message of 2017-08-15 14:11:05 +0200: > On 08/08/2017 03:30 PM, Doug Hellmann wrote: > > We realized recently that we haven't publicized some of the tools > > in the releases repository very well. One tool that will be useful > > this week as you prepare your release candidates is the 'new-release' > > command, which edits a deliverable file to add a new release from > > HEAD of the given branch, automatically computing the next verison > > number based on the inputs. > > > > Use the ``venv`` tox environment to run the tool, like this: > > > > $ tox -e venv -- new-release SERIES DELIVERABLE TYPE > > > > The SERIES value should be the release series, such as "pike". > > > > The DELIVERABLE value should be the deliverable name, such as > > "oslo.config" or "cinder". > > > > The TYPE value should be one of "bugfix", "feature", "major", > > "milestone", or "rc". > > > > If the most recent release of cinder during the pike series is > > 11.0.0.0b3 then running: > > > > $ tox -e venv -- new-release pike cinder rc > > On systems with Python 3 by default this fails on installing > lazr.restfulclient. > I think we should add > > basepython = python2 > > for now. We should definitely address that. We need lazr.restfulclient to talk to Launchpad, and we need that in the release scripts in release-tools but I don't think we need it in the releases repo. Maybe we can remove the dependency, or set it up so it is only installed when python 2 is used? Happy-to-review-patches-ly, 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
Re: [openstack-dev] [release][ptl] tools for creating new releases
On 08/08/2017 03:30 PM, Doug Hellmann wrote: We realized recently that we haven't publicized some of the tools in the releases repository very well. One tool that will be useful this week as you prepare your release candidates is the 'new-release' command, which edits a deliverable file to add a new release from HEAD of the given branch, automatically computing the next verison number based on the inputs. Use the ``venv`` tox environment to run the tool, like this: $ tox -e venv -- new-release SERIES DELIVERABLE TYPE The SERIES value should be the release series, such as "pike". The DELIVERABLE value should be the deliverable name, such as "oslo.config" or "cinder". The TYPE value should be one of "bugfix", "feature", "major", "milestone", or "rc". If the most recent release of cinder during the pike series is 11.0.0.0b3 then running: $ tox -e venv -- new-release pike cinder rc On systems with Python 3 by default this fails on installing lazr.restfulclient. I think we should add basepython = python2 for now. detects that this is the first release candidate and updates the file deliverables/pike/cinder.yaml with the new release 11.0.0.0rc1 and instructions to create a new stable branch at that tag. There are some more details in the README.rst file in the releases repository, and as usual you'll find us in #openstack-release if you have questions. 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 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] [release][ptl] tools for creating new releases
Excerpts from Armando M.'s message of 2017-08-08 08:48:34 -0700: > On 8 August 2017 at 06:30, Doug Hellmann wrote: > > > We realized recently that we haven't publicized some of the tools > > in the releases repository very well. One tool that will be useful > > this week as you prepare your release candidates is the 'new-release' > > command, which edits a deliverable file to add a new release from > > HEAD of the given branch, automatically computing the next verison > > number based on the inputs. > > > > Use the ``venv`` tox environment to run the tool, like this: > > > >$ tox -e venv -- new-release SERIES DELIVERABLE TYPE > > > > The SERIES value should be the release series, such as "pike". > > > > The DELIVERABLE value should be the deliverable name, such as > > "oslo.config" or "cinder". > > > > The TYPE value should be one of "bugfix", "feature", "major", > > "milestone", or "rc". > > > > If the most recent release of cinder during the pike series is > > 11.0.0.0b3 then running: > > > >$ tox -e venv -- new-release pike cinder rc > > > > detects that this is the first release candidate and updates the > > file deliverables/pike/cinder.yaml with the new release 11.0.0.0rc1 > > and instructions to create a new stable branch at that tag. > > > > There are some more details in the README.rst file in the releases > > repository, and as usual you'll find us in #openstack-release if you > > have questions. > > > > I tried it and it works like a charm, though I noticed some harmless side > effects in that changes [1] in my patch showed up unsolicited. Changing booleans from true/false to yes/no is a side-effect of some of the settings in the YAML formatter. Doug > > Cheers, > Armando > > [1] > https://review.openstack.org/#/c/491560/1/deliverables/pike/networking-bgpvpn.yaml@7 > > > > > 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 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] [release][ptl] tools for creating new releases
On 8 August 2017 at 06:30, Doug Hellmann wrote: > We realized recently that we haven't publicized some of the tools > in the releases repository very well. One tool that will be useful > this week as you prepare your release candidates is the 'new-release' > command, which edits a deliverable file to add a new release from > HEAD of the given branch, automatically computing the next verison > number based on the inputs. > > Use the ``venv`` tox environment to run the tool, like this: > >$ tox -e venv -- new-release SERIES DELIVERABLE TYPE > > The SERIES value should be the release series, such as "pike". > > The DELIVERABLE value should be the deliverable name, such as > "oslo.config" or "cinder". > > The TYPE value should be one of "bugfix", "feature", "major", > "milestone", or "rc". > > If the most recent release of cinder during the pike series is > 11.0.0.0b3 then running: > >$ tox -e venv -- new-release pike cinder rc > > detects that this is the first release candidate and updates the > file deliverables/pike/cinder.yaml with the new release 11.0.0.0rc1 > and instructions to create a new stable branch at that tag. > > There are some more details in the README.rst file in the releases > repository, and as usual you'll find us in #openstack-release if you > have questions. > I tried it and it works like a charm, though I noticed some harmless side effects in that changes [1] in my patch showed up unsolicited. Cheers, Armando [1] https://review.openstack.org/#/c/491560/1/deliverables/pike/networking-bgpvpn.yaml@7 > > 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 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
