Le 09/02/2015 à 11:21, Jacques Le Roux a écrit :
Le 06/02/2015 17:27, Ron Wheeler a écrit : If there are a lot of required
issues, then make it a community project to release it and get it done.
If it is not clear about the state of a release branch, then have a meeting and
make a decision.
Either it is
a) still under development and unstable or
b) it is a release candidate and only a defined and agreed upon set of bugs will be fixed before it is released and other low priority bugs and
backports will get done in the next minor release. If a new critical bug is found after it is declared a RC, then the team gets to decide if it
is included and adds it to the priority list or defers it.
If it is deferred, add a note in the release notes that an important bug is not fixed in the release but is or will be available as a patch to
the version in the trunk or development branch.
This is not rocket science and if it done properly, in an organized way, it will be clear to Adrian and everyone how any backporting or bug
fixing should be done.
Wait, we have already a rule about that. Yours are maybe not rocket science but
are too complicated IMO.
Do you have a link to the desription of the rule?
No but you can create it in the wiki using what I wrote below
Done
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=7766050&selectedPageVersions=42&selectedPageVersions=41
Jacques
