You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Phil Steitz <ph...@gmail.com> on 2011/08/05 07:08:09 UTC
Deploying snapshot builds
Looks like we have been experimenting with this. Before actually
turning anything on, we need should agree that we actually want to
to do this and probably VOTE, as I assume the generated artifacts
are going to be publicly available. My personal opinion is that we
should not do this.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Deploying snapshot builds
Posted by Henri Yandell <fl...@gmail.com>.
To quote the Infra team; ENOCARE :)
Now, if you're going to deploy the Maven generated website
automatically, I may care.
Hen
On Thu, Aug 4, 2011 at 10:57 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> We can hold a vote. I would be persuaded to vote no if someone could point to an ASF or incubator policy that says we should not do this.
>
> Ralph
>
> On Aug 4, 2011, at 10:08 PM, Phil Steitz wrote:
>
>> Looks like we have been experimenting with this. Before actually
>> turning anything on, we need should agree that we actually want to
>> to do this and probably VOTE, as I assume the generated artifacts
>> are going to be publicly available. My personal opinion is that we
>> should not do this.
>>
>> Phil
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Deploying snapshot builds
Posted by Ralph Goers <ra...@dslextreme.com>.
We can hold a vote. I would be persuaded to vote no if someone could point to an ASF or incubator policy that says we should not do this.
Ralph
On Aug 4, 2011, at 10:08 PM, Phil Steitz wrote:
> Looks like we have been experimenting with this. Before actually
> turning anything on, we need should agree that we actually want to
> to do this and probably VOTE, as I assume the generated artifacts
> are going to be publicly available. My personal opinion is that we
> should not do this.
>
> Phil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Deploying snapshot builds
Posted by Matt Benson <gu...@gmail.com>.
I don't see any harm in providing the snapshot builds. I have
personally deployed some on an ad-hoc basis to make it easier to
develop other sandbox-level libraries against the snapshots while
waiting for e.g. lang3 to be released.
Matt
On Fri, Aug 5, 2011 at 1:45 AM, Emmanuel Bourg <eb...@apache.org> wrote:
> If we are going to vote let's make a decision per project. I originally
> brought this issue up because I wanted to provide snapshots for cli and
> configuration to people willing to try out new features/bug fixes.
>
> As I understand math is probably not interested in having daily snapshots, I
> don't know for the other components.
>
> Emmanuel Bourg
>
>
> Le 05/08/2011 07:08, Phil Steitz a écrit :
>>
>> Looks like we have been experimenting with this. Before actually
>> turning anything on, we need should agree that we actually want to
>> to do this and probably VOTE, as I assume the generated artifacts
>> are going to be publicly available. My personal opinion is that we
>> should not do this.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Deploying snapshot builds
Posted by Ralph Goers <ra...@dslextreme.com>.
I didn't read Emmanuel's response that way. If we vote to allow publishing snapshots not every project should have to do that, but they would all be allowed to. I would not be in favor of a vote that forces every project to publish snapshots.
Ralph
On Aug 5, 2011, at 7:51 AM, Phil Steitz wrote:
> On 8/4/11 11:45 PM, Emmanuel Bourg wrote:
>> If we are going to vote let's make a decision per project.
>
> No, I think this needs to be decided at the Commons level. The PMC
> are collectively responsible for what we publish where. In the
> past, we have ad hoc published snapshots for individual components,
> asking if there were objections here on the list first - essentially
> lazy consensus VOTE. We have also produced nightly builds - again
> agreeing on how / where they would be published. We are now talking
> about automated generation of snapshots for some (all?) components
> on some (daily? change-triggered?) schedule. The PMC needs to agree
> to that.
>
> Phil
>> I originally brought this issue up because I wanted to provide
>> snapshots for cli and configuration to people willing to try out
>> new features/bug fixes.
>>
>> As I understand math is probably not interested in having daily
>> snapshots, I don't know for the other components.
>>
>> Emmanuel Bourg
>>
>>
>> Le 05/08/2011 07:08, Phil Steitz a écrit :
>>> Looks like we have been experimenting with this. Before actually
>>> turning anything on, we need should agree that we actually want to
>>> to do this and probably VOTE, as I assume the generated artifacts
>>> are going to be publicly available. My personal opinion is that we
>>> should not do this.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Deploying snapshot builds
Posted by Simone Tripodi <si...@apache.org>.
I agree with Phil, there should be a general agreement
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
On Fri, Aug 5, 2011 at 4:51 PM, Phil Steitz <ph...@gmail.com> wrote:
> On 8/4/11 11:45 PM, Emmanuel Bourg wrote:
>> If we are going to vote let's make a decision per project.
>
> No, I think this needs to be decided at the Commons level. The PMC
> are collectively responsible for what we publish where. In the
> past, we have ad hoc published snapshots for individual components,
> asking if there were objections here on the list first - essentially
> lazy consensus VOTE. We have also produced nightly builds - again
> agreeing on how / where they would be published. We are now talking
> about automated generation of snapshots for some (all?) components
> on some (daily? change-triggered?) schedule. The PMC needs to agree
> to that.
>
> Phil
>> I originally brought this issue up because I wanted to provide
>> snapshots for cli and configuration to people willing to try out
>> new features/bug fixes.
>>
>> As I understand math is probably not interested in having daily
>> snapshots, I don't know for the other components.
>>
>> Emmanuel Bourg
>>
>>
>> Le 05/08/2011 07:08, Phil Steitz a écrit :
>>> Looks like we have been experimenting with this. Before actually
>>> turning anything on, we need should agree that we actually want to
>>> to do this and probably VOTE, as I assume the generated artifacts
>>> are going to be publicly available. My personal opinion is that we
>>> should not do this.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Deploying snapshot builds
Posted by Gary Gregory <ga...@gmail.com>.
It would be nice to have consistency. I dream of a day where pom.xml's
are so different from component to component :)
Gary
On Fri, Aug 5, 2011 at 10:51 AM, Phil Steitz <ph...@gmail.com> wrote:
> On 8/4/11 11:45 PM, Emmanuel Bourg wrote:
>> If we are going to vote let's make a decision per project.
>
> No, I think this needs to be decided at the Commons level. The PMC
> are collectively responsible for what we publish where. In the
> past, we have ad hoc published snapshots for individual components,
> asking if there were objections here on the list first - essentially
> lazy consensus VOTE. We have also produced nightly builds - again
> agreeing on how / where they would be published. We are now talking
> about automated generation of snapshots for some (all?) components
> on some (daily? change-triggered?) schedule. The PMC needs to agree
> to that.
>
> Phil
>> I originally brought this issue up because I wanted to provide
>> snapshots for cli and configuration to people willing to try out
>> new features/bug fixes.
>>
>> As I understand math is probably not interested in having daily
>> snapshots, I don't know for the other components.
>>
>> Emmanuel Bourg
>>
>>
>> Le 05/08/2011 07:08, Phil Steitz a écrit :
>>> Looks like we have been experimenting with this. Before actually
>>> turning anything on, we need should agree that we actually want to
>>> to do this and probably VOTE, as I assume the generated artifacts
>>> are going to be publicly available. My personal opinion is that we
>>> should not do this.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Thank you,
Gary
http://garygregory.wordpress.com/
http://garygregory.com/
http://people.apache.org/~ggregory/
http://twitter.com/GaryGregory
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Deploying snapshot builds
Posted by Phil Steitz <ph...@gmail.com>.
On 8/4/11 11:45 PM, Emmanuel Bourg wrote:
> If we are going to vote let's make a decision per project.
No, I think this needs to be decided at the Commons level. The PMC
are collectively responsible for what we publish where. In the
past, we have ad hoc published snapshots for individual components,
asking if there were objections here on the list first - essentially
lazy consensus VOTE. We have also produced nightly builds - again
agreeing on how / where they would be published. We are now talking
about automated generation of snapshots for some (all?) components
on some (daily? change-triggered?) schedule. The PMC needs to agree
to that.
Phil
> I originally brought this issue up because I wanted to provide
> snapshots for cli and configuration to people willing to try out
> new features/bug fixes.
>
> As I understand math is probably not interested in having daily
> snapshots, I don't know for the other components.
>
> Emmanuel Bourg
>
>
> Le 05/08/2011 07:08, Phil Steitz a écrit :
>> Looks like we have been experimenting with this. Before actually
>> turning anything on, we need should agree that we actually want to
>> to do this and probably VOTE, as I assume the generated artifacts
>> are going to be publicly available. My personal opinion is that we
>> should not do this.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Deploying snapshot builds
Posted by Emmanuel Bourg <eb...@apache.org>.
If we are going to vote let's make a decision per project. I originally
brought this issue up because I wanted to provide snapshots for cli and
configuration to people willing to try out new features/bug fixes.
As I understand math is probably not interested in having daily
snapshots, I don't know for the other components.
Emmanuel Bourg
Le 05/08/2011 07:08, Phil Steitz a écrit :
> Looks like we have been experimenting with this. Before actually
> turning anything on, we need should agree that we actually want to
> to do this and probably VOTE, as I assume the generated artifacts
> are going to be publicly available. My personal opinion is that we
> should not do this.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org