Le 20/05/2012 13:43, Milamber a ecrit : > > Le 20/05/2012 12:31, sebb a ecrit : > >> On 20 May 2012 11:46, Milamber <milam...@apache.org> wrote: >> >> >>> Le 20/05/2012 11:06, sebb a ecrit : >>> >>> >>>> Buildbot tries to upload the Maven jars; this only works if the >>>> version is a SNAPSHOT version. >>>> >>>> In the past, we did not have Maven jars, so this was not really a >>>> problem, but I think for *future* releases we need to ensure that >>>> trunk only ever contains a SNAPSHOT version. >>>> This will allow Buildbot to deploy any jars it builds (and developers >>>> if they so desire). >>>> >>>> The method I have used for Maven builds (e.g. Commons) is as follows: >>>> >>>> * get trunk up to date (except versions) >>>> * check out clean copy of trunk into new workspace >>>> * update versions in the new workspace >>>> * create the SVN tag from the new workspace (as it's a workspace, the >>>> commit message only shows the changes from trunk) >>>> >>>> The RC can then be built in the new workspace. >>>> >>>> If problems are found with the build, update trunk to fix them, and >>>> start again with another new workspace. >>>> >>>> When the RC vote succeeds, trunk can be updated to the next SNAPSHOT. >>>> >>>> Does this make sense? >>>> >>>> >>>> >>>> >>> Yes. ok for me (for next releases) >>> I will update the wiki page Releases Creation after the end of current >>> process release 2.7 >>> >>> >> Given that the release needs to be redone, perhaps it would be useful >> to try the process out for the next release candidate? >> Would you be willing to try that? >> >> > Yes I will try this process out for the 2.7RC2. >
I've published a update for release process. http://wiki.apache.org/jmeter/ReleaseCreation Milamber > Milamber > > > >> >> >>> Milamber >>> >>> >>> >>> >>> >>> >> >> > >
