I don't have much of an opinion.  Whichever you think is best.  I
think as long as it's still available somewhere (and it looks like
archive.a.o does that already) and it doesn't break people who may be
using it as a Maven dependency (or is there no way around this?).

+1 on a non-incubator LARQ release, even if there are no changes
except removing "incubator"

-Stephen


On Wed, Aug 1, 2012 at 5:16 AM, Andy Seaborne <[email protected]> wrote:
> (after some prompting by infra)
>
> We have still got
>
> http://www.apache.org/dist/incubator/jena/
>
> I've removed the old artifacts (actually, taken a copy of everything) for
> stuff now released as a TLP.  This leaves LARQ there.
>
> To complete the clean up we could do one of:
>
> 1/ put all the incubator artifacts into svnpubsub then immediately delete
> them.  Effect: they never appear in /dist/jena/ and, as I understand it,
> never go to archive.a.o/dist/jena
>
> 2/ As (1) but expose for 4 (? 24) hours so archive.apache.org puts them in
> its dist/jena area and then delete them.
>
> Effect: They appear briefly in /dist/jena/ and get archived in
> archive.a.o/dist/jena
>
> (I'm assuming they go in with the current layout binaries/ and source/
> layout, not that of the incubator releases per rmodule
>
> 3/ (2) except layout is /dist/jena/incubator/... i.e exact layout as is but
> in a different location.
>
> 4/ Leave as is - leave larq in /dist/incubator/jena/
>
> 5/ Something else.
>
> For LARQ, can be do a 1.0.1 release to get it out withour "-incubating"?
>
> Thoughts?
>
>     Andy

Reply via email to