Hello everybody,
maybe I overlooked the answer to the question in the *subject* in the
mail thread. I am all fine with Christian Schultes definitions, but
would be really be interested in pulling alphas from repo1/central.
What is the current agreement here?
So +1 for publishing to central from
Am 02/26/17 um 13:03 schrieb Stephen Connolly:
> Even if we had a -1 as long as I have the binding votes *as release
> manager* it would be my call whether to release or not.
>
> Now *personally* I much rather release with consensus, but any committer
> can step up to be release manager for any
Even if we had a -1 as long as I have the binding votes *as release
manager* it would be my call whether to release or not.
Now *personally* I much rather release with consensus, but any committer
can step up to be release manager for any of our components, so I would
prefer if we can agree our
Hi,
On 26/02/17 12:22, Hervé BOUTEMY wrote:
now I see your reasoning
3.3.n were expected to be final quality: they were not, they were dropped (vote
result was -1, result sent to trash)
That is the difference here. The alpha-1 at the moment does not have any
-1 yet...(not that I seen one,
now I see your reasoning
3.3.n were expected to be final quality: they were not, they were dropped (vote
result was -1, result sent to trash)
3.5.0-alpha-n is expected to be alpha quality: from tests, we have the alpha
quality (IMHO even more quality, but not final quality), then the vote will
On Sun, 26 Feb 2017 04:58:24 +0100, Manfred Moser
wrote:
Imho it should go to Central just like any other release. All components
and everything. The version clearly tells thats its alpha and this
allows for clean testing, embedding and so on.
We have done it
+1 to release to central
there are general questions on what goes into central (and how central
contains probably many unused versions of artifacts), but our Maven core
release is not the right moment to try to work on every question we ignored
until now
Regards,
Hervé
Le samedi 25 février
>From my PoV Alpha versions, compared to betas, are those which can be used
only with user's risk unlike betas which are stable however need feedback
to make them yet official release version.
What makes sense among these two versions to deploy alpha to Central?
On Sun, Feb 26, 2017 at 4:59 AM,
Let's deploy. I don't see any risk to do it. The version name is clear
enough to warn people to use it for tests only.
(And I am so motivated to update the Jenkins evil plugin ;) )
Le dim. 26 févr. 2017 à 11:00, Karl Heinz Marbaise a
écrit :
> Hi,
>
> my opinion is cleary to
Hi,
my opinion is cleary to deploy to central as we did before...to give
others a chance to test.
I can often see that many people are automatically downloading Maven
from Central (download from Apache dist etc. is not a good idea apart
from that blocked) for example with travis, ship-it,
Am 02/25/17 um 22:55 schrieb Karl Heinz Marbaise:
> Hi,
>
> based on the started discussion about either to bring 3.5.0-alpha-1 to
> Central or not I would suggest to discuss in a separate thread and
> prevent using the VOTE's threads for that (as Stephen already mentioned).
>
> Using Central:
Imho it should go to Central just like any other release. All components and
everything. The version clearly tells thats its alpha and this allows for clean
testing, embedding and so on.
We have done it in the past and I dont see any reason for changing this.
Manfred
Stephen Connolly wrote
So if I am embedding Maven, how do I embed Maven 3.5.0-alpha-1?
(I know it should not be a big issue as we should have the release soon
anyway, but more from the principal POV)
Consider the Jenkins "evil" job type plugin that has dependencies on some
of the artifacts that are in the staging
It depends on what the task of Central is. If it for *dependencies*,
there's no need to publish pre-final versions; don't think we should
motive plugins to depend on alphas.
AFAIK the common way to get a new version of Maven is via
http://maven.apache.org/download.cgi and not via Central.
I don't see a reason not to push 3.5.0-alpha-1 to Central. It has been
done this way for previous versions, and makes it more broadly
applicable for all users.
Guillaume
Le 25/02/2017 à 22:55, Karl Heinz Marbaise a écrit :
Hi,
based on the started discussion about either to bring
My view is we should release to central.
I am not so strongly held of this view that I would object to
alternatives... but I do think just dropping the staging repo and pushing
the src to dist would be a bad plan
On Sat 25 Feb 2017 at 21:56, Karl Heinz Marbaise wrote:
> Hi,
Hi,
based on the started discussion about either to bring 3.5.0-alpha-1 to
Central or not I would suggest to discuss in a separate thread and
prevent using the VOTE's threads for that (as Stephen already mentioned).
Using Central:
o Everybody can use it and make tests on it.
Using an other
17 matches
Mail list logo