Vote results:
+5 binding
+3 advisory
According to recommendations I will:
* promote the project
* fix the discrepancies
* make another release and post it for the vote.
Thanks everyone voted!
Oleg
Jason van Zyl wrote:
On 6-Oct-08, at 9:45 PM, Brett Porter wrote:
Sorry, I mistranslated my notes and missed the most important thing -
the POMs still contain references to 1.0.0-alpha-1-SNAPSHOT
properties as well.
Those are just property values, left over by the release plugin. Real
depen
On 6-Oct-08, at 9:45 PM, Brett Porter wrote:
Sorry, I mistranslated my notes and missed the most important thing
- the POMs still contain references to 1.0.0-alpha-1-SNAPSHOT
properties as well.
- Brett
On 07/10/2008, at 3:39 PM, Brett Porter wrote:
The current release artifacts have a nu
Oleg,
The first step here now I think will be the promotion of Mercury out
of the sandbox. Once the promotion is done we can quickly stage
another release. Let's get past the promotion first.
On 3-Oct-08, at 10:02 PM, Oleg Gusakov wrote:
I open this vote to release mercury 1.0.0-alpha-1 an
+1
Oleg Gusakov wrote:
I open this vote to release mercury 1.0.0-alpha-1 and promote it out of
sandbox, so that we can start using the transport piece - mercury wagon
- right away.
For the past several months a group of some 5 community members has been
working on Mercury - http://docs.codeh
+1
Emmanuel
On Tue, Oct 7, 2008 at 11:29 AM, Jesse McConnell
<[EMAIL PROTECTED]>wrote:
> based on the clarification, I am +1 to promote mercury and get it into a
> position for more mainstream usage and trial
>
> jesse
>
> On Sat, Oct 4, 2008 at 11:09 AM, Oleg Gusakov
> <[EMAIL PROTECTED]>wrote:
based on the clarification, I am +1 to promote mercury and get it into a
position for more mainstream usage and trial
jesse
On Sat, Oct 4, 2008 at 11:09 AM, Oleg Gusakov
<[EMAIL PROTECTED]>wrote:
> Clarification: this vote is for promoting mercury and start using mercury
> wagon.
>
> Ralph - can
Sorry, I mistranslated my notes and missed the most important thing -
the POMs still contain references to 1.0.0-alpha-1-SNAPSHOT properties
as well.
- Brett
On 07/10/2008, at 3:39 PM, Brett Porter wrote:
The current release artifacts have a number of problems. At first
glance:
- the SCM
The current release artifacts have a number of problems. At first
glance:
- the SCM will be pinned to the sandbox, one reason we generally
promote first, then release.
- the POMs still contain references to sonatype repositories
- I don't think mercury-it can be released due to GPL dependencie
+1
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 07, 2008 12:05 AM
To: Maven Developers List
Subject: Re: [VOTE] release and promote Mercury 1.0.0-alpha-1
+1
On 4-Oct-08, at 1:02 AM, Oleg Gusakov wrote:
> I open this vote to release merc
+1
On 4-Oct-08, at 1:02 AM, Oleg Gusakov wrote:
I open this vote to release mercury 1.0.0-alpha-1 and promote it out
of sandbox, so that we can start using the transport piece - mercury
wagon - right away.
For the past several months a group of some 5 community members has
been working o
Let's discuss this on Thursday. We just need to make sure to write up
summary emails from the day and post them back to the list for further
discussion.
Ralph
Oleg Gusakov wrote:
Ralph Goers wrote:
I have no problem with including the wagon. I've read the wiki pages
on Mercury and I'm not
If the Mercury wagon passes the unit tests I have no problem with
incorporating it. However, my +1 is only advisory (as is yours) since I
am not a member of the Maven PMC.
Ralph
Oleg Gusakov wrote:
Clarification: this vote is for promoting mercury and start using
mercury wagon.
Ralph - can
Clarification: this vote is for promoting mercury and start using
mercury wagon.
Ralph - can I count you as +1 on this vote?
All other discussions - like dependency resolution - are outside of that
scope. Sorry for bringing those up in this thread.
Oleg
Ralph Goers wrote:
I have no problem
Ralph Goers wrote:
I have no problem with including the wagon. I've read the wiki pages
on Mercury and I'm not satisifed with the dependecy resolution
improvements. As I've said before, any scheme that relies only on
resolving artifact versions isn't going to solve the problem.
Ralph,
Probl
On 4-Oct-08, at 3:30 AM, Ralph Goers wrote:
I have no problem with including the wagon. I've read the wiki pages
on Mercury and I'm not satisifed with the dependecy resolution
improvements. As I've said before, any scheme that relies only on
resolving artifact versions isn't going to solve
I have no problem with including the wagon. I've read the wiki pages on
Mercury and I'm not satisifed with the dependecy resolution
improvements. As I've said before, any scheme that relies only on
resolving artifact versions isn't going to solve the problem.
We can talk more about this on Thu
Jason Dillon wrote:
+1
Will this also include the non-transport bits? I'm looking to consume
those in gshell ASAP to replace maven-artifact.
Not all of them - there is still one piece missing. I will document the
exact status and progress in more detail in a separate jira
Thanks,
Oleg
--
+1
Will this also include the non-transport bits? I'm looking to consume
those in gshell ASAP to replace maven-artifact.
--jason
On Oct 4, 2008, at 12:02 PM, Oleg Gusakov wrote:
I open this vote to release mercury 1.0.0-alpha-1 and promote it out
of sandbox, so that we can start using t
I open this vote to release mercury 1.0.0-alpha-1 and promote it out of
sandbox, so that we can start using the transport piece - mercury wagon
- right away.
For the past several months a group of some 5 community members has been
working on Mercury - http://docs.codehaus.org/display/MAVEN/Mer
20 matches
Mail list logo
