Re: The Future of the Release Process.

2006-12-19 Thread Antoine Levy-Lambert

Hello Joakim,

I like this discussion, I am a big fan of automating the release  
process.


I also have some hands on experience being RM for Ant 1.6 and 1.7.

For Ant 1.7, we are using what you call the staged release process.

When I prepare a build, I have to assume that the vote on the  
binaries will be positive and prepare everything with a release  
version in mind.


Tagging the release should to my opinion happen between preparing and  
staging the release.


To make sure everything is clean, the SVN sandbox could be recreated  
based on the tag.


When I did my first build of ANT 1.7.0 last week, someone checked  
code in between the time when I created my SVN sandbox and the time  
when I created my tag.
In the end, this change was included in the tag but not in my build.  
Bad ...  See [1] the command used to create the tag


Also, creating a branch for a release is optional. Right now we are  
releasing Ant 1.7.0 from the trunk, and we

do not have a ANT_17_BRANCH.

Suggested modifications for your staged release process :

c) 'prepare' release (occurs once)
  * Create a branch using provided Branch ID for this release.
  * Update poms in branch to provided Release Version ID.
+* Optionally update documentation in branch to provided  
Release Version ID.
  * Update poms in trunk to provided Next Development  
Version ID.


 +  d) tag the release (occurs 1 or more times)

 +  e) create a new SVN sandbox using the tag created in d)

 -  d) stage release (occurs 1 or more times)
 +  f) 'stage' release (occurs 1 or more times)


It would be cool if you could persist your ideas concerning the  
release process to a document in SVN or to a Wiki page.


Regards,

Antoine


[1]
svn copy https://svn.apache.org/repos/asf/ant/core/trunk \
https://svn.apache.org/repos/asf/ant/core/tags/ANT_170 \
-m "Tagging version 1.7.0 of Ant"

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [sandbox-openpgp] does maven really already use openpgp ?

2006-10-30 Thread Antoine Levy-Lambert
Hello Brett,

I am surprised by the concept of making a listener write the signature.
Since the listener is working (I believe) on the build machine end and not on 
the repository end, there must be a mechanism to add the signature files to the 
list of files to transfer ? Does the listener "know" which files to sign (you 
probably want to sign jars, wars, zip, tgz and bz2 files, but not the md5 and 
sha1 files) ? Also where would you tell maven to attach this listener to the 
upload process ? in POM files ? or code it in different wagon providers ?

Concerning the web site of openpgp, I will rephrase the text to say that there 
is work in progress in wagon-openpgp.

Regards,

Antoine
 Original-Nachricht 
Datum: Tue, 31 Oct 2006 06:26:48 +1100
Von: Brett Porter <[EMAIL PROTECTED]>
An: "Maven Developers List" 
Betreff: Re: [sandbox-openpgp] does maven really already use openpgp ?

> I think it was true when I wrote it, but without proper integration I  
> didn't commit the changes to trunk as it would have been too disruptive.
> 
> Still, wagon-openpgp does exist and between that and commons-openpgp  
> that's most of the work.
> 
> http://svn.apache.org/repos/asf/maven/wagon/trunk/wagon-openpgp/src/ 
> main/java/org/apache/maven/wagon/openpgp/
> 
> See also:
> http://docs.codehaus.org/display/MAVEN/Repository+Security+Improvements
> 
> - Brett
> 
> On 31/10/2006, at 4:41 AM, Antoine Levy-Lambert wrote:
> 
> > Hi,
> >
> > I just read this on the web site of openpgp :
> >
> > http://jakarta.apache.org/commons/sandbox/openpgp/
> >
> > "Currently, Maven uses it in its development version to sign  
> > libraries released to the repository."
> >
> > Is this true ? Is there a mojo which does it ? In which codebase is  
> > this mojo ?
> >
> > Regards,
> >
> > Antoine
> >

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sandbox-openpgp] does maven really already use openpgp ?

2006-10-30 Thread Antoine Levy-Lambert
Hi,

I just read this on the web site of openpgp :

http://jakarta.apache.org/commons/sandbox/openpgp/

"Currently, Maven uses it in its development version to sign libraries released 
to the repository."

Is this true ? Is there a mojo which does it ? In which codebase is this mojo ?

Regards,

Antoine

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [jira] Commented: (MAVENUPLOAD-971) please upload maven-site-plugin 2.0-SNAPSHOT

2006-07-03 Thread Antoine Levy-Lambert
Hello Brett,

thanks,

regards,

Antoine

Brett Porter wrote:
> I had some uncommitted changes. It should work now.
>
> - Brett
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [jira] Commented: (MAVENUPLOAD-971) please upload maven-site-plugin 2.0-SNAPSHOT

2006-07-02 Thread Antoine Levy-Lambert
Hello Carlos,

sorry to bother you.

You say that I should add this section to the pom.xml of commons-sandbox :

  
org.apache
apache
1


and remove the repository part : it is already commented out.

With these changes in the pom.xml of the commons-sandbox I still cannot
build openpgp.

Would you mind downloading the sources of common-sanbox and get openpgp
to build ?

If you are sure of yourself, could you post a message in commons-dev
explaining exactly what needs to be changed in each POM ?

Regards,

Antoine


Carlos Sanchez (JIRA) wrote:
> [ 
> http://jira.codehaus.org/browse/MAVENUPLOAD-971?page=comments#action_68785 ] 
>
> Carlos Sanchez commented on MAVENUPLOAD-971:
> 
>
> That pom is not configured properly with the apache snapshot repository, 
> 2.0-SNAPSHOT is already there
> It's commented in that thread
>
>   
>> please upload maven-site-plugin 2.0-SNAPSHOT
>> 
>>
>>  Key: MAVENUPLOAD-971
>>  URL: http://jira.codehaus.org/browse/MAVENUPLOAD-971
>>  Project: maven-upload-requests
>> Type: Task
>> 
>
>   
>> Reporter: Antoine Levy-Lambert
>> 
>
>   
>> In order to build openpgp with  maven 2.0.4 I need maven-site-plugin 
>> 2.0-SNAPSHOT.
>> I do not know where this dependency comes from (why is a SNAPSHOT version 
>> required rather than a released version, and which other maven plugin is 
>> triggering this dependency).
>> I have checked out maven-site-plugin from source and installed it, this is a 
>> workaround.
>> But in order that other maven users do not have to do this, it would be good 
>> to upload a 2.0-SNAPSHOT version of maven-site-plugin.
>> Regards,
>> Antoine
>> I have found this message thread 
>> http://www.nabble.com/Running-maven-site-plugin-from-svn-tf1462915.html#a3953978
>>   which shows that other maven users seem to need it too.
>> 
>
>   


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]