Open Stack

OK, thanks for the input. I'll get the patches out to enable this by Friday
this week, once Mitaka-1 is cut for Neutron.

On Wed, Dec 2, 2015 at 11:34 AM, Brandon Logan <brandon.logan at rackspace.com>
wrote:

> Makes complete sense.
>
> On Wed, 2015-12-02 at 10:38 -0600, Kyle Mestery wrote:
> > We're hoping to cut Neutron M-1 this week [1]. We have implemented
> > release notes in the main Neutron repository [2] , but not in the *aaS
> > repositories. At the time, I thought this was a good approach and we
> > could collect all releasenotes there. But I think it makes sense to
> > have releasenotes in the *aaS repositories as well.
> >
> > What I'm going to propose is we cut Neutron M-1 as-is now, with any
> > *aaS releasenotes done in the main repository. Once Neutron M-1 is
> > cut, I'll add the releasenotes stuff into the *aaS repositories, and
> > we can start using releasenotes independently in those repositories.
> >
> > If anyone has issues with this approach please reply on this thread.
> >
> > Thanks!
> > Kyle
> >
> > [1] https://review.openstack.org/#/c/251959/
> > [2] https://review.openstack.org/241758
> >
> >
> __________________________________________________________________________
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151202/9cd2986e/attachment.html>