Since the patches for layer 3 networking automation has been merged, I
think we'd better include the patches for resource cleaning in the tagged
branch. Here is the list:

Floating ip deletion: https://review.openstack.org/354604
Subnet cleaning: https://review.openstack.org/355847
Router cleaning: https://review.openstack.org/360848

Shinobu Kinjo <shinobu...@gmail.com>于2016年9月20日周二 下午12:04写道:

> This announcement should have been first to avoid any unnecessary work -;
>
> On Tue, Sep 20, 2016 at 12:51 PM, joehuang <joehu...@huawei.com> wrote:
> > Hello, as the Trio2o repository has been established, it's time for us to
> > discuss the freeze date and tagging(newton branch) for the last release
> of
> > Tricircle with gateway function.
> >
> > The freeze date is the gate for patches to be merged before
> tagging(newton
> > branch). If a patch can't finish review process before the freeze date,
> and
> > not able to be merged in Tricircle, then it's suggested to be handled
> like
> > this:
> >
> > 1. If it's networking automation related patch, continue the review
> process
> > in Tricircle after tagging(newton branch), will be merged in Tricircle
> trunk
> > in the future .
> >
> > 2. If it's gateway related patch, abandon the patch, re-submit the patch
> in
> > Trio2o.
> >
> > 3. If it's patch about pod management, for it's common feature, so
> continue
> > the review process in tricircle  after tagging(newton branch) , and
> submit a
> > new patch for this feature in Trio2o separately.
> >
> > Exception request after freeze date, before tagging(newton branch): If
> there
> > is some patch must be merged before the tagging(newton branch), then
> need to
> > send the exception request in the mail-list for the patch, and approved
> by
> > PTL.
> >
> > That means we need to define a deadline for patches to be merged in
> > Tricircle before tagging(newton branch), and define the scope of patches
> > wish to be merged in Trcircle before splitting.
> >
> > Your thoughts, proposal for the freeze date and patches to be merged?
> >
> > (As the old thread containing both Trio2o and Tricircle in the subject,
> not
> > good to follow, so a new thread is started)
> >
> > Best Regards
> > Chaoyi Huang (joehuang)
> >
> > ________________________________
> > From: joehuang
> > Sent: 18 September 2016 16:34
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: RE: [openstack-dev] [tricircle][trio2o] trio2o git repo ready
> and
> > tricircle splitting
> >
> > Thank you for your comment, Zhiyuan.
> >
> > For pod management, because these two projects need to run
> independently, I
> > think submit patches separately as needed may be a better choice.
> >
> > Best Regards
> > Chaoyi Huang(joehuang)
> > ________________________________
> > From: Vega Cai [luckyveg...@gmail.com]
> > Sent: 18 September 2016 16:27
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [tricircle][trio2o] trio2o git repo ready
> and
> > tricircle splitting
> >
> > +1 for the proposal. What about the codes for Pod operation? It seems
> that
> > both Tricircle and Trio2o need these codes. We submit patches to these
> two
> > projects separately?
> >
> > Zhiyuan
> >
> > joehuang <joehu...@huawei.com>于2016年9月18日周日 下午4:17写道:
> >>
> >> hello, team,
> >>
> >> Trio2o git repository is ready now: https://github.com/openstack/trio2o
> >>
> >> The repository inherited all files and commit messages from Tricircle.
> >>
> >> It's now the time start to do the tricircle splitting: a blue print is
> >> registere for Tricircle cleaning:
> >>
> https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron.There
> >> are lots of documentation work to do. Please review these doc in the BP,
> >> thanks.
> >>
> >> There are some proposal for patches during the splitting:
> >>
> >> 1. For patch which is already in review status, let's review it in
> >> Tricircle (no matter it's for Trio2o or Tricircle), after it's get
> merged,
> >> then port it to Trio2o. After all patches get merged, let's have a last
> tag
> >> for Tricircle to cover both gateway and networking automation function.
> Then
> >> the cleaning will be done in Tricircle to make Tricircle as a project
> for
> >> networking automation only
> >> 2. For new patch which is only applicable to Trio2o, I propose that we
> >> submit such patches in Trio2o only, no need to submit in Tricircle.
> >>
> >> Would like to know your thoughts on the splitting.
> >>
> >> Best Regards
> >> Chaoyi Huang(joehuang)
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> __________________________________________________________________________
> >> 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
> >
>
>
>
> --
> Email:
> shin...@linux.com
> shin...@redhat.com
>
> __________________________________________________________________________
> 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
>
-- 
BR
Zhiyuan
__________________________________________________________________________
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

Reply via email to