Re: [openstack-dev] [congress] following up on releasing kilo milestone 2
I will take a close look and see what mods I need to make. Or we could just move the congress repo :) Thanks for reaching out on this. On Thursday, February 12, 2015, Thierry Carrez thie...@openstack.org wrote: Thierry Carrez wrote: You could also try to use the milestone.sh release script I use: http://git.openstack.org/cgit/openstack-infra/release-tools/tree/ Hrm... I now realize the script is forcing openstack/* namespace and won't work as-is for stackforge projects. That repo is accepting patches, though :) -- 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 -- ~sean __ 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] [congress] following up on releasing kilo milestone 2
sean roberts wrote: so git checkout master git pull https://git.openstack.org/stackforge/congress.git dbef982ea72822e0b7acc16da9b6ac89d3cf3530 git tag -s 2015.1.0b2 git push gerrit 2015.1.0b2 You could also try to use the milestone.sh release script I use: http://git.openstack.org/cgit/openstack-infra/release-tools/tree/ It will push the tag, wait for the tarball to be generated, turn all FixCommitted bugs in Launchpad into FixReleased for the milestone, and upload the tarball to Launchpad. It relies on a few assumptions on the Launchpad part (in particular that only the Launchpad bugs fixed during the current milestone are in FixCommitted state, and that your Launchpad milestone is called kilo-2), but otherwise should work. Don't hesitate to ask me questions about it if you have any. -- 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] [congress] following up on releasing kilo milestone 2
Thierry Carrez wrote: You could also try to use the milestone.sh release script I use: http://git.openstack.org/cgit/openstack-infra/release-tools/tree/ Hrm... I now realize the script is forcing openstack/* namespace and won't work as-is for stackforge projects. That repo is accepting patches, though :) -- 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] [congress] following up on releasing kilo milestone 2
sean roberts seanrobert...@gmail.com writes: At our last meeting I volunteered to figure out what we need to do for milestone 2. Here is what I propose: Repo cleanup: We tag today's release with 2015.1.0b2. This is copying tag the other openstack projects are using. I believe below is the correct syntax. Let me know if there is a cleaner way and/or if setting the head pointer to a specific commit is more accurate. git checkout master git pull --ff-only git tag -s 2015.1.0b2 git push gerrit 2015.1.0b2 Yes, this matches: http://docs.openstack.org/infra/manual/drivers.html#tagging-a-release But yes, if you want to tag a specific commit instead of the tip of master, you can do that. -Jim __ 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] [congress] following up on releasing kilo milestone 2
At our last meeting I volunteered to figure out what we need to do for milestone 2. Here is what I propose: Repo cleanup: We tag today's release with 2015.1.0b2. This is copying tag the other openstack projects are using. I believe below is the correct syntax. Let me know if there is a cleaner way and/or if setting the head pointer to a specific commit is more accurate. git checkout master git pull --ff-only git tag -s 2015.1.0b2 git push gerrit 2015.1.0b2 Launchpad cleanup: I move all the blueprints and bugs from the juno series and kilo m1 to kilo m2. I then remove the juno series and kilo m1. I release kilo m2. I upload the congress tar file kilo m2. Next Steps: We target releasing kilo m3 on 19 march and repeating most of the above steps. I won't be deleting any milestones or series this time. We also target releasing the congress kilo release on 30 april. ~ sean __ 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] [congress] following up on releasing kilo milestone 2
so git checkout master git pull https://git.openstack.org/stackforge/congress.git dbef982ea72822e0b7acc16da9b6ac89d3cf3530 git tag -s 2015.1.0b2 git push gerrit 2015.1.0b2 On Wed, Feb 11, 2015 at 5:26 PM, James E. Blair cor...@inaugust.com wrote: sean roberts seanrobert...@gmail.com writes: At our last meeting I volunteered to figure out what we need to do for milestone 2. Here is what I propose: Repo cleanup: We tag today's release with 2015.1.0b2. This is copying tag the other openstack projects are using. I believe below is the correct syntax. Let me know if there is a cleaner way and/or if setting the head pointer to a specific commit is more accurate. git checkout master git pull --ff-only git tag -s 2015.1.0b2 git push gerrit 2015.1.0b2 Yes, this matches: http://docs.openstack.org/infra/manual/drivers.html#tagging-a-release But yes, if you want to tag a specific commit instead of the tip of master, you can do that. -Jim __ 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 -- ~ sean __ 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
