Just so there is no misunderstanding: I'm neither for nor against doing releases. I'm fine either way.
Would we release all our content at the same time? Or would we release every bit separately? Releasing everything separately would probably become a burden quite soon. Would we do it on a timed schedule or when someone feels like it? Most of our content commits could probably stand on its own and could be released after each commit. We can't really meaningful vote on hundreds of releases per year (of course hoping we'll get that much content). On Thu, May 16, 2019 at 1:09 AM Justin Mclean <[email protected]> wrote: > Hi, > > > That's a good point but again other projects do similar things, no? > > One example is ComDev. Are the things they produce (e.g. content) being > > "released" properly? Some of it just pops up on their homepage. > > Documentation is seen as different true. In this case the slides do also > contain some code (phython, poms and the like) so it may not be considered > just documentation. I agree it’s not clear cut. > > Perhaps this also helps [1] "Generically, a release is anything that is > published beyond the group that owns it. For an Apache project, that means > any publication outside the development community, defined as individuals > actively participating in development or following the dev list.” Given we > want people outside our development community to use it is look like we > probably need to make releases. > > If we want to make convenient zips / tars of things and use the ASF > distribution mechanise we would certainly need to make releases. > > Thanks, > Justin > > 1. http://www.apache.org/legal/release-policy.html#release-definition > >
