Great! Thanks for the update From: "Armando M." <arma...@gmail.com> Reply-To: OpenStack List <openstack-dev@lists.openstack.org> Date: Monday, March 6, 2017 at 5:03 PM To: OpenStack List <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [neutron][sfc][release] stable/ocata version
On 5 March 2017 at 23:24, Ihar Hrachyshka <ihrac...@redhat.com<mailto:ihrac...@redhat.com>> wrote: With https://review.openstack.org/#/c/437699/ in, stadium projects will no longer have any other option but to follow the common schedule. That change is new for Pike+ so we may still see some issues with Ocata release process. The stable branch for Ocata is being cut in [1]. Everything else that targets Pike is a go. [1] https://review.openstack.org/#/c/439200/ Ihar On Sun, Mar 5, 2017 at 8:03 PM, Jeffrey Zhang <zhang.lei....@gmail.com<mailto:zhang.lei....@gmail.com>> wrote: > Add [release] tag in subject. > > Do not follow the OpenStack release schedule will cause lots of issues. Like > requirements changes, patches is merged which should not be merged into > stable. > > It also may break the deploy project release schedule( like Kolla will not > be > released until sfc release ocata branch and tag ). > > I hope sfc team could follow the OpenStack release schedule, even though it > may > cause some cherry-pick, but it is safer and how OpenStack project live. > > > On Sun, Mar 5, 2017 at 3:44 PM, Gary Kotton > <gkot...@vmware.com<mailto:gkot...@vmware.com>> wrote: >> >> Please note that things are going to start to get messy now – there are >> changes in neutron that break master and these will affect the cutting of >> the stable version. One example is https://review.openstack.org/441654 >> >> >> >> So I suggest cutting a stable ASAP and then cherrypicking patches >> >> >> >> From: Gary Kotton <gkot...@vmware.com<mailto:gkot...@vmware.com>> >> Reply-To: OpenStack List >> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> >> Date: Sunday, March 5, 2017 at 9:36 AM >> >> >> To: OpenStack List >> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> >> Subject: Re: [openstack-dev] [neutron][sfc] stable/ocata version >> >> >> >> Thanks! >> >> >> >> From: Jeffrey Zhang <zhang.lei....@gmail.com<mailto:zhang.lei....@gmail.com>> >> Reply-To: OpenStack List >> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> >> Date: Sunday, March 5, 2017 at 9:12 AM >> To: OpenStack List >> <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> >> Subject: Re: [openstack-dev] [neutron][sfc] stable/ocata version >> >> >> >> This is talked in [0]. sfc team said >> >> >> >> > we will pull a stable/ocata branch around end of Feb or early March the >> > latest. >> >> >> >> [0] >> http://lists.openstack.org/pipermail/openstack-dev/2017-February/112580.html >> >> >> >> On Sun, Mar 5, 2017 at 3:01 PM, Gary Kotton >> <gkot...@vmware.com<mailto:gkot...@vmware.com>> wrote: >> >> Hi, >> >> We are pretty blocked at the moment with our gating on stable/ocata. This >> is due to the fact that there is no networking-sfc version tagged for ocata. >> >> Is there any ETA for this? >> >> Thanks >> >> Gary >> >> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> >> >> >> -- >> >> Regards, >> >> Jeffrey Zhang >> >> Blog: >> http://xcodest.me<https://urldefense.proofpoint.com/v2/url?u=http-3A__xcodest.me&d=DwMFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw&m=e9oFxLk6K7GOvDVL0y3uKlSTQHtU9tnXcMGHL46H37I&s=9fysx1MmSeqhencLNvi8w-M1Ryv8UPPz6Mdx6bUkveA&e=> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > > -- > Regards, > Jeffrey Zhang > Blog: > http://xcodest.me<https://urldefense.proofpoint.com/v2/url?u=http-3A__xcodest.me&d=DwMFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=PMrZQUSXojEgJQPh7cZrz1Lvja0OwAstg0U82FalZrw&m=e9oFxLk6K7GOvDVL0y3uKlSTQHtU9tnXcMGHL46H37I&s=9fysx1MmSeqhencLNvi8w-M1Ryv8UPPz6Mdx6bUkveA&e=> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://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://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
