commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Neidhart <thomas.neidh...@gmail.com>
Subject Re: [collections] Release 4.0-alpha1 to maven?
Date Fri, 05 Jul 2013 19:44:26 GMT
On 07/05/2013 10:24 AM, Thomas Neidhart 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?

Ok, I see there is a lot of controversial discussion about this topic.

Personally, I think it should be fine to release alpha versions to maven
central, and the respective users / developers who rely on this library
should take care of updating their products accordingly once the final
is released (if they are really willing to depend on an alpha release in
the first place).

But I can also understand the concern that if commons-collections4 will
be used a lot (ok, let's hope for it), and that dangling dependencies to
an alpha release will just create headache for nothing.

So, as release manager, I decide to go the safe route, and do not
publish to maven central.

I will keep the release on the staging repository, so it should also be
easily accessible via maven, although we may not be able to advertise it
(I am unsure about the rules here). Once 4.0-final is released and
published, the staging repo for 4.0-alpha1 will be dropped.

Thomas

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message