Is it documented somewhere what constitutes a release per Apache conventions? I would imagine that a PMC could decide that certain releases are only made on Maven Central and only specific releases are made as binary and source bundles that go through the Apache mirroring/archive system.
Doing a release only via a specific channel doesn't mean that we wouldn't have to do the usual process for voting etc. -- Richard On 03.12.2013, at 18:33, Marshall Schor <[email protected]> wrote: > hmmm, > > Apache projects are not allowed to "publish" things without doing the release > process. > > I think the main principle would be: > > For addons, do a "release" of each one whenever it seems appropriate, and > then, > From time to time - do a bundled milestone release (like Eclipse). > > Of course, that's more work :-( ... > > -Marshall > > On 11/28/2013 9:19 AM, Richard Eckart de Castilho wrote: >> That's what I mean, yes. >> >> -- Richard >> >> On 28.11.2013, at 12:10, Jens Grivolla <[email protected]> wrote: >> >>> On 11/28/2013 01:48 PM, Richard Eckart de Castilho wrote: >>>> For the addons, we might consider not having a separate folder for each >>>> addon, and neither do source/binary releases for each release of an >>>> individual >>>> addon. Instead, we might consider doing bundled milestone releases (like >>>> Eclipse) >>>> every once in a while. >>> Do you mean to publish maven artifacts of individual addons whenever they >>> get updated, but only do releases for download from the UIMA page once in a >>> while? That sounds like a very good option to me... >>> >>> -- Jens
