What is the procedure for issues with patches for both 0.26.1 and trunk? I would suggest that once committed to trunk the issue can be marked as resolved but it must be given a target of 0.26.1 so that someone can find the issues later.
Either that or it remains open till committed to both. Any views? Bob. 2008/10/4 Linus Tolke <[EMAIL PROTECTED]> > Hello Christian! > > trunk (anywhere) is not a part of this and shouldn't be used for anything > related to the 0.26.1 (and other 0.26.* releases). > > The automated tagging and creating subclipse tag/branch marks will only > work from trunk so you will have to do that manually. I think we can forget > about the subclipse tag/branch marks this time. They are not important. > > Since there is a patch, we don't need the work branch or we could decide > that for every issue that is a candidate. > > You will have to create the branch for the releases. I suggest we call it > BRANCH_0_26 and put it in branches. > > What you do is > > - For all projects involved in the release you create the branch using > some command like: > svn copy > > http://<project>.tigris.org/svn/<project>/releases/VERSION_0_26<http://%3Cproject%3E.tigris.org/svn/%3Cproject%3E/releases/VERSION_0_26> > > http://<project>.tigris.org/svn/<project>/branches/BRANCH_0_26<http://%3Cproject%3E.tigris.org/svn/%3Cproject%3E/branches/BRANCH_0_26> > - Commit all patches in that branch. > - Do the final testing against a switched-to checked-out copy > - We create the release tag (by copying back to releases/VERSION_0_26_1 > for all projects) > - Then, I will let the automated release script can check out and > build. > > While doing the 0.26 release I wanted the versions of the java web start to > be shortened (i.e. not reference the ALPHA/BETAs) but when then doing the > 0.27.1 release I noticed that the java web start script messes it up and > don't use the 0.26 to build on but the betas. In this case it means that I > will continue to maintain the list of versions for the java web start jars > manually. > > /Linus > > > > > > 2008/10/3 Christian López Espínola <[EMAIL PROTECTED]> > > Hi, >> >> Tom Morris said: >> > I think it should be done as soon as we can get fixes for all the >> > P1/P2 bugs and an appropriate amount of testing done. >> > >> >> Shall we do this soon? This weekend? >> > >> > Since Christian volunteered to establish the branch and Linus >> > approves, can't the work start as soon as Christian is available? I'm >> > not sure what other planning needs to be done. As soon as all the >> > fixes are committed and tested, the build can be done whenever Linus >> > has time available. >> >> I think that I can dedicate time for it this weekend. >> I will create the branch, reproduce the bugs, patch them and verify >> that they're solved. >> >> Bob asks for a 0.26.1 milestone, but we can discuss about what will go >> there until Linus creates it in IZ. >> I'm sure that we agree on 5428 (profile issue) and 5420 (ToDo items >> issue, needs patch reviewing). >> >> I linked to the P3 fixed issues (5256 and 5258) because they are (now >> fixed) bugs, not new features, though they don't have a high priority. >> IMHO we could include it, but I understand if you don't want to. >> >> Question, maybe for Linus: >> Should we branch trunk/ or just argouml-app/? I think (have to verify) >> that all the patches are for the argouml-app project, but don't know >> what is easier for adapting the release scripts. >> >> > Tom >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> >> >> -- >> Cheers, >> >> Christian López Espínola <penyaskito> >> > >
