On 7/5/13 4:35 AM, Gary Gregory wrote: > Over at log4j we release betas to maven central. I think we should do > so here too for alphas. It's just too much of a pain to use a jar in a > build otherwise.
Do you subsequently introduce incompatible API changes with no package name change in the "stable" releases? That's what I would worry about here. Collections is so widely used / depended on that having API-incompatible versions with the same package name eternally in the wild would seem a bad idea to me. Phil > > Gary > > On Jul 5, 2013, at 4:24, Thomas Neidhart <thomas.neidh...@gmail.com> wrote: > >> Hi, >> >> just to make sure we have agreement on this topic. >> Reading again the thread about release alpha/beta releases I think we did >> not reach consensus whether to publish alpha releases to maven central. >> >> It would be easier for people to try out things, but the release will stay >> there forever and some people had objections against it. >> >> We also know for sure that the API will change, as we will at least rename >> one new class introduced for 4.0 (CompliantBag -> CollectionBag). >> >> So the questions is: >> >> Shall we publish to maven central? >> >> Thomas > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > . > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
