[openstack-dev] [neutron] Release Notes for *aaS projects

Doug Wiegley dougwig at parksidesoftware.com
Wed Dec 2 18:05:15 UTC 2015


I’m in favor of things living in the repo where their code lives. The fewer dependencies the better. Especially if we stop adding them. So, I agree.

doug


> On Dec 2, 2015, at 9:38 AM, Kyle Mestery <mestery at mestery.com> 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




More information about the OpenStack-dev mailing list