Hi Jochen, Jochen Wiedmann wrote:
> On Sat, Sep 2, 2017 at 12:50 AM, Gilles <gil...@harfang.homelinux.org> > wrote: > >> Because of "Commons" rules, it is not "equivalent": There was >> a long thread concluding that all modules must be released >> _together_, and with the same top-level package name and version >> number. >> It is very "maintainer(s)-unfriendly" because of the quite >> different subject matters that coexist in CM. > > I wouldn't count that rule "*all* modules must be released" as a mantra: > > a) In case of an emergency release (fixing a CVE, for example), I'd > clearly consider pushing out the module as more important than waiting > for a full release. (Of course, one must be careful to maintain > compatibility when pushing out just a module, but that goes without > saying.) > b) I'd like to hear others experiences on that topic (maybe VFS). > Anyways, my personal experiences with Rat are clear: Releasing *all* > together is causing nothing but pain, and tends to defer releases > indefinitely. OTOH, releasing a submodule can be done at all times, > and without overly much preparation. > > In conclusion, I'd definitely support the release of a single > submodule, if the need would arise. Just that our tooling does not support this: 1/ No proper support for release of a GIT subtree 2/ No proper support for such a site generation 3/ No proper support using the release plugin 4/ Parents of such a component will have their own release cycle ... - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
