You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Jeremy Boynes <jb...@apache.org> on 2006/10/06 21:30:39 UTC

[RESULT] Release parent pom and buildtools for M2

This got PPMC +1's from jboynes, dkulp, jmarino, rineholt, rfeng,  
bdaniel, kwilliams
and +1 from Luciano Resende

However, there are significant abstentions from antelder,  
kelvingoodson and svkrish on the basis that the purpose of releasing  
this is unclear.

In light of this confusion I think it would be unwise to proceed to  
the IPMC and so am going to withdraw these artifacts. We need to come  
up with an alternative plan for the release which everyone is clear on.

--
Jeremy

On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:

> The parent pom and buildtools are pre-reqs for all other Java  
> projects in the M2 release. These are distributed through the maven  
> repo rather than as a end-user distribution. Please vote to approve  
> the release content:
>
> parent-pom
> [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/ 
> java-pom-parent/1
> [binary] http://people.apache.org/repo/m2-incubating-repository/org/ 
> apache/tuscany/parent/1-incubator/
>
> buildtools
> [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/ 
> java-buildtools/1.0-incubator-M2
> [binary] http://people.apache.org/repo/m2-incubating-repository/org/ 
> apache/tuscany/buildtools/1.0-incubator-M2/
>
> Here's my +1
> --
> Jeremy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>


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


Re: [RESULT] Release parent pom and buildtools for M2

Posted by kelvin goodson <ke...@gmail.com>.
"Here Here" to Venkat's words of support,  and FWIW, in the same spirit of
trusting those who have gone before,  here's my +1.

Regards, Kelvin.

On 07/10/06, Venkata Krishnan <fo...@gmail.com> wrote:
>
> Hi Jeremy,
>
> My abstinence is only due to me not possessing enough knowledge not only
> of
> what it is but more of what it should best be.  While your explanation
> here
> has really helped (thanks for that) to understand what this is about, I am
> yet to reach a position where I can 'evaluate / review' it.
>
> I hope to be catching up on all of this soon, but did not push myself just
> now since I believed that there were enough (and infact more) votes in its
> favour to go forward - I assumed that my abstinence is never going to be a
> blocker.
>
> My abstinence is most certainly not to mean what has been proposed is
> suspect.  I sincerely apologize if that has created such an impression
> after
> all the hard work you are putting in as Release Manager.  I
> whole-heartedly
> trust and acknowledge the value of the votes that have been cast in its
> favour (including yours) and in that spirit, to get out of the way to the
> release....
>
> Here is my +1.... :)
>
> - Venkat
>
> On 10/7/06, Jeremy Boynes <jb...@apache.org> wrote:
> >
> > This got PPMC +1's from jboynes, dkulp, jmarino, rineholt, rfeng,
> > bdaniel, kwilliams
> > and +1 from Luciano Resende
> >
> > However, there are significant abstentions from antelder,
> > kelvingoodson and svkrish on the basis that the purpose of releasing
> > this is unclear.
> >
> > In light of this confusion I think it would be unwise to proceed to
> > the IPMC and so am going to withdraw these artifacts. We need to come
> > up with an alternative plan for the release which everyone is clear on.
> >
> > --
> > Jeremy
> >
> > On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:
> >
> > > The parent pom and buildtools are pre-reqs for all other Java
> > > projects in the M2 release. These are distributed through the maven
> > > repo rather than as a end-user distribution. Please vote to approve
> > > the release content:
> > >
> > > parent-pom
> > > [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/
> > > java-pom-parent/1
> > > [binary] http://people.apache.org/repo/m2-incubating-repository/org/
> > > apache/tuscany/parent/1-incubator/
> > >
> > > buildtools
> > > [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/
> > > java-buildtools/1.0-incubator-M2
> > > [binary] http://people.apache.org/repo/m2-incubating-repository/org/
> > > apache/tuscany/buildtools/1.0-incubator-M2/
> > >
> > > Here's my +1
> > > --
> > > Jeremy
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>
>

Re: [RESULT] Release parent pom and buildtools for M2

Posted by Venkata Krishnan <fo...@gmail.com>.
Hi Jeremy,

My abstinence is only due to me not possessing enough knowledge not only of
what it is but more of what it should best be.  While your explanation here
has really helped (thanks for that) to understand what this is about, I am
yet to reach a position where I can 'evaluate / review' it.

I hope to be catching up on all of this soon, but did not push myself just
now since I believed that there were enough (and infact more) votes in its
favour to go forward - I assumed that my abstinence is never going to be a
blocker.

My abstinence is most certainly not to mean what has been proposed is
suspect.  I sincerely apologize if that has created such an impression after
all the hard work you are putting in as Release Manager.  I whole-heartedly
trust and acknowledge the value of the votes that have been cast in its
favour (including yours) and in that spirit, to get out of the way to the
release....

Here is my +1.... :)

- Venkat

On 10/7/06, Jeremy Boynes <jb...@apache.org> wrote:
>
> This got PPMC +1's from jboynes, dkulp, jmarino, rineholt, rfeng,
> bdaniel, kwilliams
> and +1 from Luciano Resende
>
> However, there are significant abstentions from antelder,
> kelvingoodson and svkrish on the basis that the purpose of releasing
> this is unclear.
>
> In light of this confusion I think it would be unwise to proceed to
> the IPMC and so am going to withdraw these artifacts. We need to come
> up with an alternative plan for the release which everyone is clear on.
>
> --
> Jeremy
>
> On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:
>
> > The parent pom and buildtools are pre-reqs for all other Java
> > projects in the M2 release. These are distributed through the maven
> > repo rather than as a end-user distribution. Please vote to approve
> > the release content:
> >
> > parent-pom
> > [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/
> > java-pom-parent/1
> > [binary] http://people.apache.org/repo/m2-incubating-repository/org/
> > apache/tuscany/parent/1-incubator/
> >
> > buildtools
> > [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/
> > java-buildtools/1.0-incubator-M2
> > [binary] http://people.apache.org/repo/m2-incubating-repository/org/
> > apache/tuscany/buildtools/1.0-incubator-M2/
> >
> > Here's my +1
> > --
> > Jeremy
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>

Re: [RESULT] Release parent pom and buildtools for M2

Posted by Jeremy Boynes <jb...@apache.org>.
On Oct 7, 2006, at 10:08 PM, Luciano Resende wrote:

> We could start with your previous post, and maybe take a portion of  
> Monday's
> IRC Chat to go over Q&A or clarifications ? Does that sound good ?

Happy to chat on Monday (but remember it's a holiday in some parts of  
the world and people may be traveling for ApacheCon).

Q&A on this list though has the advantage that those not present can  
participate and that the discussion is archived so others can review  
later.

--
Jeremy

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


Re: [RESULT] Release parent pom and buildtools for M2

Posted by Luciano Resende <lu...@gmail.com>.
We could start with your previous post, and maybe take a portion of Monday's
IRC Chat to go over Q&A or clarifications ? Does that sound good ?

- Luciano

On 10/7/06, Jeremy Boynes <jb...@apache.org> wrote:
>
> I want to state up front there that I don't think you did any thing
> wrong or inappropriate. Far from it; I think you did exactly the
> right thing.
>
> During the vote you said you didn't have sufficient experience to
> make criticism and could we schedule a walkthrough; others agreed
> with them. This is a fairly major issue as it shows that we do not
> have a common understanding of what we are releasing here. We had
> some discussion on the list on both the technical and process aspects
> but I did not think that we had achieved that common understanding;
> from your comment below .
>
> So, although procedurally we may have had enough votes, IMO we did
> not have consensus on this release due to this unresolved issue and
> that's a serious enough problem that we should not release at this
> time. I'd vote -1, but as the person who initiated the vote that
> would be odd so I abandoned it.
>
> The task now is resolving the issue at hand - we need to come up with
> a process for this release that we all understand and agree on.
>
> I'd posted on the technical and process sides of what was going on
> last week so perhaps that would be the place to start. If not, other
> suggestions would be welcome
>
> --
> Jeremy
>
>
> On Oct 7, 2006, at 3:19 AM, kelvin goodson wrote:
>
> > It was not my intention to force a rethink.  All I asked for,  at a
> > time
> > when the vote was going slowly, was some assistance  in
> > understanding the
> > technical detail of the artifacts in order that I might further the
> > voting
> > process.  As I understood the procedure,  the vote could be carried
> > by n +1s
> > (3 i think) and no -1s, so we soon passed that mark.  Once the vote
> > had
> > passed the criteria i did not feel the immediate need to press for
> > further
> > explanation,  yet i still did not feel in a position to make a well
> > informed
> > judgement.   A core of people have given this a +1 and I trust that
> > this
> > indicates the artifacts are good.  On that basis,  if the voting
> > process
> > requires me to give an explit +1 for the vote to be carried then I
> > am happy
> > to do so.  I'm not trying to be at all awkward here,  quite the
> > reverse in
> > fact.
> >
> > Regards, Kelvin.
> >
> >
> >
> > On 06/10/06, Jim Marino <jm...@myromatours.com> wrote:
> >>
> >>
> >> On Oct 6, 2006, at 12:30 PM, Jeremy Boynes wrote:
> >>
> >> > This got PPMC +1's from jboynes, dkulp, jmarino, rineholt, rfeng,
> >> > bdaniel, kwilliams
> >> > and +1 from Luciano Resende
> >> >
> >> > However, there are significant abstentions from antelder,
> >> > kelvingoodson and svkrish on the basis that the purpose of
> >> > releasing this is unclear.
> >> >
> >> > In light of this confusion I think it would be unwise to proceed to
> >> > the IPMC and so am going to withdraw these artifacts. We need to
> >> > come up with an alternative plan for the release which everyone is
> >> > clear on.
> >> >
> >> This is unfortunate. Perhaps someone can propose an alternative
> >> approach or the abstainers could post specific questions that would
> >> clear up their uncertainty?
> >>
> >> Jim
> >> > --
> >> > Jeremy
> >> >
> >> > On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:
> >> >
> >> >> The parent pom and buildtools are pre-reqs for all other Java
> >> >> projects in the M2 release. These are distributed through the
> >> >> maven repo rather than as a end-user distribution. Please vote to
> >> >> approve the release content:
> >> >>
> >> >> parent-pom
> >> >> [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/
> >> >> java-pom-parent/1
> >> >> [binary] http://people.apache.org/repo/m2-incubating-repository/
> >> >> org/apache/tuscany/parent/1-incubator/
> >> >>
> >> >> buildtools
> >> >> [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/
> >> >> java-buildtools/1.0-incubator-M2
> >> >> [binary] http://people.apache.org/repo/m2-incubating-repository/
> >> >> org/apache/tuscany/buildtools/1.0-incubator-M2/
> >> >>
> >> >> Here's my +1
> >> >> --
> >> >> Jeremy
> >> >>
> >> >>
> >> >>
> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> >> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >> >>
> >> >
> >> >
> >> >
> >> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> >> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >> >
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>

Re: [RESULT] Release parent pom and buildtools for M2

Posted by Jeremy Boynes <jb...@apache.org>.
I want to state up front there that I don't think you did any thing  
wrong or inappropriate. Far from it; I think you did exactly the  
right thing.

During the vote you said you didn't have sufficient experience to  
make criticism and could we schedule a walkthrough; others agreed  
with them. This is a fairly major issue as it shows that we do not  
have a common understanding of what we are releasing here. We had  
some discussion on the list on both the technical and process aspects  
but I did not think that we had achieved that common understanding;  
from your comment below .

So, although procedurally we may have had enough votes, IMO we did  
not have consensus on this release due to this unresolved issue and  
that's a serious enough problem that we should not release at this  
time. I'd vote -1, but as the person who initiated the vote that  
would be odd so I abandoned it.

The task now is resolving the issue at hand - we need to come up with  
a process for this release that we all understand and agree on.

I'd posted on the technical and process sides of what was going on  
last week so perhaps that would be the place to start. If not, other  
suggestions would be welcome

--
Jeremy


On Oct 7, 2006, at 3:19 AM, kelvin goodson wrote:

> It was not my intention to force a rethink.  All I asked for,  at a  
> time
> when the vote was going slowly, was some assistance  in  
> understanding the
> technical detail of the artifacts in order that I might further the  
> voting
> process.  As I understood the procedure,  the vote could be carried  
> by n +1s
> (3 i think) and no -1s, so we soon passed that mark.  Once the vote  
> had
> passed the criteria i did not feel the immediate need to press for  
> further
> explanation,  yet i still did not feel in a position to make a well  
> informed
> judgement.   A core of people have given this a +1 and I trust that  
> this
> indicates the artifacts are good.  On that basis,  if the voting  
> process
> requires me to give an explit +1 for the vote to be carried then I  
> am happy
> to do so.  I'm not trying to be at all awkward here,  quite the  
> reverse in
> fact.
>
> Regards, Kelvin.
>
>
>
> On 06/10/06, Jim Marino <jm...@myromatours.com> wrote:
>>
>>
>> On Oct 6, 2006, at 12:30 PM, Jeremy Boynes wrote:
>>
>> > This got PPMC +1's from jboynes, dkulp, jmarino, rineholt, rfeng,
>> > bdaniel, kwilliams
>> > and +1 from Luciano Resende
>> >
>> > However, there are significant abstentions from antelder,
>> > kelvingoodson and svkrish on the basis that the purpose of
>> > releasing this is unclear.
>> >
>> > In light of this confusion I think it would be unwise to proceed to
>> > the IPMC and so am going to withdraw these artifacts. We need to
>> > come up with an alternative plan for the release which everyone is
>> > clear on.
>> >
>> This is unfortunate. Perhaps someone can propose an alternative
>> approach or the abstainers could post specific questions that would
>> clear up their uncertainty?
>>
>> Jim
>> > --
>> > Jeremy
>> >
>> > On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:
>> >
>> >> The parent pom and buildtools are pre-reqs for all other Java
>> >> projects in the M2 release. These are distributed through the
>> >> maven repo rather than as a end-user distribution. Please vote to
>> >> approve the release content:
>> >>
>> >> parent-pom
>> >> [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/
>> >> java-pom-parent/1
>> >> [binary] http://people.apache.org/repo/m2-incubating-repository/
>> >> org/apache/tuscany/parent/1-incubator/
>> >>
>> >> buildtools
>> >> [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/
>> >> java-buildtools/1.0-incubator-M2
>> >> [binary] http://people.apache.org/repo/m2-incubating-repository/
>> >> org/apache/tuscany/buildtools/1.0-incubator-M2/
>> >>
>> >> Here's my +1
>> >> --
>> >> Jeremy
>> >>
>> >>
>> >>  
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> >>
>> >
>> >
>> >  
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> >
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>


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


Re: [RESULT] Release parent pom and buildtools for M2

Posted by kelvin goodson <ke...@gmail.com>.
It was not my intention to force a rethink.  All I asked for,  at a time
when the vote was going slowly, was some assistance  in understanding the
technical detail of the artifacts in order that I might further the voting
process.  As I understood the procedure,  the vote could be carried by n +1s
(3 i think) and no -1s, so we soon passed that mark.  Once the vote had
passed the criteria i did not feel the immediate need to press for further
explanation,  yet i still did not feel in a position to make a well informed
judgement.   A core of people have given this a +1 and I trust that this
indicates the artifacts are good.  On that basis,  if the voting process
requires me to give an explit +1 for the vote to be carried then I am happy
to do so.  I'm not trying to be at all awkward here,  quite the reverse in
fact.

Regards, Kelvin.



On 06/10/06, Jim Marino <jm...@myromatours.com> wrote:
>
>
> On Oct 6, 2006, at 12:30 PM, Jeremy Boynes wrote:
>
> > This got PPMC +1's from jboynes, dkulp, jmarino, rineholt, rfeng,
> > bdaniel, kwilliams
> > and +1 from Luciano Resende
> >
> > However, there are significant abstentions from antelder,
> > kelvingoodson and svkrish on the basis that the purpose of
> > releasing this is unclear.
> >
> > In light of this confusion I think it would be unwise to proceed to
> > the IPMC and so am going to withdraw these artifacts. We need to
> > come up with an alternative plan for the release which everyone is
> > clear on.
> >
> This is unfortunate. Perhaps someone can propose an alternative
> approach or the abstainers could post specific questions that would
> clear up their uncertainty?
>
> Jim
> > --
> > Jeremy
> >
> > On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:
> >
> >> The parent pom and buildtools are pre-reqs for all other Java
> >> projects in the M2 release. These are distributed through the
> >> maven repo rather than as a end-user distribution. Please vote to
> >> approve the release content:
> >>
> >> parent-pom
> >> [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/
> >> java-pom-parent/1
> >> [binary] http://people.apache.org/repo/m2-incubating-repository/
> >> org/apache/tuscany/parent/1-incubator/
> >>
> >> buildtools
> >> [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/
> >> java-buildtools/1.0-incubator-M2
> >> [binary] http://people.apache.org/repo/m2-incubating-repository/
> >> org/apache/tuscany/buildtools/1.0-incubator-M2/
> >>
> >> Here's my +1
> >> --
> >> Jeremy
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>

Re: [RESULT] Release parent pom and buildtools for M2

Posted by Jim Marino <jm...@myromatours.com>.
On Oct 6, 2006, at 12:30 PM, Jeremy Boynes wrote:

> This got PPMC +1's from jboynes, dkulp, jmarino, rineholt, rfeng,  
> bdaniel, kwilliams
> and +1 from Luciano Resende
>
> However, there are significant abstentions from antelder,  
> kelvingoodson and svkrish on the basis that the purpose of  
> releasing this is unclear.
>
> In light of this confusion I think it would be unwise to proceed to  
> the IPMC and so am going to withdraw these artifacts. We need to  
> come up with an alternative plan for the release which everyone is  
> clear on.
>
This is unfortunate. Perhaps someone can propose an alternative  
approach or the abstainers could post specific questions that would  
clear up their uncertainty?

Jim
> --
> Jeremy
>
> On Oct 2, 2006, at 8:28 AM, Jeremy Boynes wrote:
>
>> The parent pom and buildtools are pre-reqs for all other Java  
>> projects in the M2 release. These are distributed through the  
>> maven repo rather than as a end-user distribution. Please vote to  
>> approve the release content:
>>
>> parent-pom
>> [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/ 
>> java-pom-parent/1
>> [binary] http://people.apache.org/repo/m2-incubating-repository/ 
>> org/apache/tuscany/parent/1-incubator/
>>
>> buildtools
>> [tag]    https://svn.apache.org/repos/asf/incubator/tuscany/tags/ 
>> java-buildtools/1.0-incubator-M2
>> [binary] http://people.apache.org/repo/m2-incubating-repository/ 
>> org/apache/tuscany/buildtools/1.0-incubator-M2/
>>
>> Here's my +1
>> --
>> Jeremy
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>


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