otify the sender and delete this email from your system. Thank
you.
Brett Porter <[EMAIL PROTECTED]>
08/23/2006 10:37 PM
Please respond to
continuum-dev@maven.apache.org
To
continuum-dev@maven.apache.org
cc
Subject
Re: Release Management for Maven/Continuum
The summary page shows on
24/2006 05:51 PM
Please respond to
continuum-dev@maven.apache.org
To
continuum-dev@maven.apache.org
cc
Subject
Re: Release Management for Maven/Continuum
Hi all,
After talking with Jason I have started on phase 1 of this venture.
Phase 1 is as follows:
1. Create a model for Mave
proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you received this email in error,
please notify the sender and delete this email from your system. Thank
you.
Brett Porter <[EMAIL PROTECTED]>
08/23/2006 10:37 PM
Please respond to
continuum-dev@
<[EMAIL PROTECTED]>
08/23/2006 10:37 PM
Please respond to
continuum-dev@maven.apache.org
To
continuum-dev@maven.apache.org
cc
Subject
Re: Release Management for Maven/Continuum
> The summary page shows only a few of the release parameters. So the
> "Edit" link is there
RELEASE-130
Jason has given me some good tips and such and I plan on starting
this
tomorrow sometime. If any of you have any concerns, complaints or
suggestions, please let me know.
Take care,
Jeremy
--
View this message in context: http://www.nabble.com/Release-
Management-for-Maven-Continuum-tf1771971.html#a5947006
Sent from the Continuum - Dev forum at Nabble.com.
The original proposal was web services based, but the entire
process occurring from Continuum is definitely useful. I think the
concrete drivers are:
Right, so like other stuff there is a backend service, and it is
exposed in the same way to both a web interface and an xmlrpc client,
but
On 23 Aug 06, at 10:02 AM 23 Aug 06, Brett Porter wrote:
Finally getting around to replying :)
I spoke to Edwin on IRC and he's proposed the following steps:
1) go to the project group...
2) then click on the release project icon ( a new icon )
3) then a page will prompt for the release versio
ra.codehaus.org/browse/CONTINUUM-727
>> http://jira.codehaus.org/browse/MRELEASE-130
>>
>> Jason has given me some good tips and such and I plan on starting this
>> tomorrow sometime. If any of you have any concerns, complaints or
>> suggestions, please let me know.
>>
>> Take care,
>>
>> Jeremy
>
>
--
View this message in context:
http://www.nabble.com/Release-Management-for-Maven-Continuum-tf1771971.html#a5947006
Sent from the Continuum - Dev forum at Nabble.com.
On 24/08/2006, at 12:17 AM, Joakim Erdfelt wrote:
Some thoughts.
I could see the need to go back into the build history and creating
a release off of an older build to be quite likely too.
absolutely. I think Jason has talked about checking in the release
model and tagging that in the pa
Some thoughts.
I could see the need to go back into the build history and creating a
release off of an older build to be quite likely too.
Also, should the locking of the project be at the Continuum/filesystem
side, or on the SCM side? If scm side, we should add
supportsLock()/lock()/unlock
Finally getting around to replying :)
I spoke to Edwin on IRC and he's proposed the following steps:
1) go to the project group...
2) then click on the release project icon ( a new icon )
3) then a page will prompt for the release version and the next dev
version...
4) after filling the require
11 matches
Mail list logo
