On Tue, Feb 10, 2015 at 9:19 AM, Doug Hellmann <d...@doughellmann.com> wrote:
> > > On Tue, Feb 10, 2015, at 07:25 AM, Sean Dague wrote: > > On 02/09/2015 10:55 PM, Michael Still wrote: > > > The previous policy is that we do a release "when requested" or when a > > > critical bug fix merges. I don't see any critical fixes awaiting > > > release, but I am not opposed to a release. > > > > > > The reason I didn't do this yesterday is that Joe wanted some time to > > > pin the stable requirements, which I believe he is still working on. > > > Let's give him some time unless this is urgent. > > > > Going forward I'd suggest that we set a goal to do a monthly nova-client > > release to get fixes out into the wild in a more regular cadence. Would > > be nice to not have this just land as a big bang release at the end of a > > cycle. > > We review the changes in Oslo libraries weekly. Is there any reason not > to do the same with client libs? Given the automation in place for > creating releases, I think the whole process (including release notes) > is down to just a few minutes now. The tagging script is in the > openstack-infra/release-tools repository and I'd be happy to put the > release notes script there, too, if others want to use it. > > ++, I'd love to see that script land there Doug! And I agree, doing this releases is fairly straightforward now, so perhaps they should occur with a more regular cadence. Thanks, Kyle > Doug > > > > > -Sean > > > > > > > > Michael > > > > > > On Tue, Feb 10, 2015 at 2:45 PM, melanie witt <melwi...@gmail.com> > wrote: > > >> On Feb 6, 2015, at 8:17, Matt Riedemann <mrie...@linux.vnet.ibm.com> > wrote: > > >> > > >>> We haven't done a release of python-novaclient in awhile (2.20.0 was > released on 2014-9-20 before the Juno release). > > >>> > > >>> It looks like there are some important feature adds and bug fixes on > master so we should do a release, specifically to pick up the change for > keystone v3 support [1]. > > >>> > > >>> So can this be done now or should this wait until closer to the Kilo > release (library releases are cheap so I don't see why we'd wait). > > >> > > >> Thanks for bringing this up -- there are indeed a lot of important > features and fixes on master. > > >> > > >> I agree we should do a release as soon as possible, and I don't think > there's any reason to wait until closer to Kilo. > > >> > > >> melanie (melwitt) > > >> > > >> > > >> > > >> > > >> > > >> > __________________________________________________________________________ > > >> 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 Dague > > http://dague.net > > > > > __________________________________________________________________________ > > 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 >
__________________________________________________________________________ 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
