12/08/2020 14:47, Bruce Richardson: > On Wed, Aug 12, 2020 at 11:29:15AM +0200, Thomas Monjalon wrote: > > The default git branch of the main DPDK repository has been renamed > > from master to main. > > > > Signed-off-by: Thomas Monjalon <tho...@monjalon.net> [...] > > -The backup maintainer for the master tree should be selected from the > > existing sub-tree maintainers from the project. > > +The backup maintainer for the main tree should be selected > > +from the existing sub-tree maintainers of the project. > > This does not need to be a straight master -> main replacement. I wonder if > "release tree" would be a better name. However, "main" is probably clear > enough, so I'm ok to keep this as suggested here.
"release tree" does not distinguish from stable releases. I agree "main" is not ideal to identify the tree, but I don't see any better wording. [...] > > Any release of DPDK can be designated as a Stable Release if a > > maintainer volunteers to maintain it and there is a commitment from major > > contributors to validate it before releases. If a release is to be > > designated > > -as a Stable Release, it should be done by 1 month after the master release. > > +as a Stable Release, it should be done by 1 month after the main release. > > Not sure if this the most readable. The term "release" might be better > replaced with "version" to allow the use of "release" as a verb for > readability. > > "Any release version of DPDK can be designated a Stable Release if ... > If a version is to be a "Stable Release", it should be designated as such > within one month of that version being initially released" You wording is a lot better. I take it, thanks. > As-is or with above suggestions, this seems fine. > > Acked-by: Bruce Richardson <bruce.richard...@intel.com> Applied with last suggestion, thanks
