I'm +1 for doing this, and offer to do some/most of the legwork to get
this to happen.
Other opinions?
If we get a concensus, I'll ask to get the setups done, so we can start
doing the needed changes.
-Marshall
2010/3/27 Marshall Schor
> I'm +1 for doing this, and offer to do some/most of the legwork to get
> this to happen.
>
> Other opinions?
>
I'm +1 too.
Tommaso
Marshall Schor wrote:
I'm +1 for doing this, and offer to do some/most of the legwork to get
this to happen.
Other opinions?
From a development point of view Hudson can help us
to make sure that our build is never broken, and if so notice us,
but usually our build always works. Not sure if i
On 3/28/2010 12:36 PM, Jörn Kottmann wrote:
> Marshall Schor wrote:
>> I'm +1 for doing this, and offer to do some/most of the legwork to get
>> this to happen.
>>
>> Other opinions?
>>
> From a development point of view Hudson can help us
> to make sure that our build is never broken, and if
Here's my vision of automation (achieved over time :-) ), and why CI
could be important - it is building the potential releases from source
checkout.
We have CI going on Hudson; we decide at some point that things merit a
release; so we push some button on the CI or Nexus interface and get a
parti
Marshall Schor wrote:
Here's my vision of automation (achieved over time :-) ), and why CI
could be important - it is building the potential releases from source
checkout.
We have CI going on Hudson; we decide at some point that things merit a
release; so we push some button on the CI or Nexus i
Yes, it really sounds nice to me too (so +1 again).
Tommaso
2010/4/6 Jörn Kottmann
> Marshall Schor wrote:
>
>> Here's my vision of automation (achieved over time :-) ), and why CI
>> could be important - it is building the potential releases from source
>> checkout.
>>
>> We have CI going on Hu
after some discussion, 3 people voted +1:
Marshall Schor
Jörn Kottmann
Tommaso Teofili
No other votes were received, and I think this is not controversial, so
I'll go ahead and start by requesting to get set up on Nexus, at least,
by doing a Jira subtask of
http://issues.apache.org/jira/browse/IN