>----- Original Message ----- >From: "Clint Byrum" <cl...@fewbar.com> >To: "openstack-dev" <openstack-dev@lists.openstack.org> >Sent: Thursday, January 16, 2014 7:29:28 PM >Subject: Re: [openstack-dev] [TripleO] milestone-proposed branches
>Note that tripleo-incubator is special and should not be released. It >is intentionally kept unfrozen and unreleased to make sure there is no >illusion of stability. Same answer I got last September. :) I understand your point, but used tripleo-incubator as an example. What I'd like to say is a tag would be cool to build a package and test of [insert official maintained project from Tripleo Wiki]. >If there are components in it that need releasing, they should be moved >into relevant projects or forked into their own projects. Excerpts from Ryan Brady's message of 2014-01-16 07:42:33 -0800: > +1 for releases. > > In the past I requested a tag for tripleo-incubator to make it easier to > build a package and test. > > In my case a common tag would be easier to track than trying to gather all of > the commit hashes where > the projects are compatible. > > Ryan > > ----- Original Message ----- > From: "James Slagle" <james.sla...@gmail.com> > To: "OpenStack Development Mailing List" <openstack-dev@lists.openstack.org> > Sent: Thursday, January 16, 2014 10:13:58 AM > Subject: [openstack-dev] [TripleO] milestone-proposed branches > > At last summit, we talked about doing stable branches and releases for > the TripleO projects for Icehouse. > > I'd like to propose doing a milestone-proposed branch[1] and tagged > release for icehouse milestones 2 and 3. Sort of as dry run and > practice, as I think it could help tease out some things we might not > have considered when we do try to do icehouse stable branches. > > The icehouse milestone 2 date is January 23rd [2]. So, if there is > concensus to do this, we probably need to get the branches created > soon, and then do any bugfixes in the branches (master too of course) > up unitl the 23rd. > > I think it'd be nice if we had a working devtest to use with the > released tarballs. This raises a couple of points: > - We probably need a way in devtest to let people use a different > branch (or tarball) of the stuff that is git cloned. > - What about tripleo-incubator itself? We've said in the past we don't > want to attempt to stabilize or release that due to it's "incubator > nature". But, if we don't have a stable set of devtest instructions > (and accompanying scripts like setup-endpoints, etc), then using an > ever changing devtest with the branches/tarballs is not likely to work > for very long. > > And yes, I'm volunteering to do the work to support the above, and the > release work :). > > Thoughts? > > [1] https://wiki.openstack.org/wiki/BranchModel > [2] https://wiki.openstack.org/wiki/Icehouse_Release_Schedule > > -- > -- James Slagle > -- > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev