[dpdk-web] [dpdk-dev] [PATCH v2] update stable releases roadmap
thomas at monjalon.net
Tue May 1 18:02:00 CEST 2018
01/05/2018 17:46, Kevin Traynor:
> On 05/01/2018 03:16 PM, Aaron Conole wrote:
> > Thomas Monjalon <thomas at monjalon.net> writes:
> >> So the questions are:
> >> - What we must wait before pushing a backport in the stable tree?
> >> - What we must wait before tagging a stable release?
> >> I think it is reasonnable to push backports one or two weeks after
> >> it is in the master branch, assuming master is tested by the community.
> >> If a corner case is found later, it will be fixed with another patch.
> > +1 - I agree here. Folks who truly care about 'validated stable'
> > (whatever definition that takes) will only use a labeled version anyway.
> > OTOH, developers who want to see that their patches are landing in
> > stable (and more over, who want to ensure that their proposed backports
> > are actually complete - which is more relevant w.r.t. hardware),
> > shouldn't have to wait for the label.
> > Most other projects work this way, as well. Keep pulling in the
> > relevant patches from master to the stable branch(es). Do the official
> > label / release at a certain point in time relative to the main release
> > (or as needed in the case of "oh no, a serious bug here").
> I agree and I think it's the best way. However, it also requires
> semi-frequent pull request merging into the master branch for this to
> work. Otherwise there is still delay, just earlier in the process.
> Not sure if there is a written/un-written workflow for when the next-*
> branches merge into master at the moment?
We try to have more pulls before RC1.
It is not formal yet.
More information about the web