The code that needs to be patched is actually in the jbosssx cvs module. I did
add a JBoss_2_2_0_Final to the code in this module at the time of the
2.2 release, but I did not make a branch.
Would this work:
cvs rtag -b -r JBoss_2_2_0_Final Branch_2_2 jbosssx
co -rBranch_2_2 jbosssx
----- Original Message -----
From: "Bordet, Simone" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 11, 2001 2:23 PM
Subject: R: [JBoss-dev] 2.2 Patch procedure
> Hey Scott,
>
> > Ok, a problem mentioned on the user list turns out to be a
> > bug in the 2.2
> > release of the JBossSX code. This was not seen because the
> > login module
> > used in the howto was not being convered in the unit tests(my fault).
> >
> > So, what is the procedure for creating a patch and new release on the
> > 2.2 branch?
>
> I can tell you what to do in CVS, I'm not expert on how this must be handled
> in SourceForge using the tracker, anyway:
>
> Checkout the 2.2 branch:
> cvs co -rBranch_2_2 jboss
>
> Change what has to be changed (working on the files you just checked out)
> and commit the changes.
>
> Tag the branch with a new tag: the next available is Rel_2_2_1, so:
> cvs tag Rel_2_2_1 (from the jboss' module root dir)
>
> Here if you think that a new JBoss release (2.2.1) is truly needed, you can
> use the JBoss_2_2_1_Final tag instead of Rel_2_2_1. It really depends on how
> much important is the bug you fixed, and maybe a word of Marc about shipping
> a new release. If you have a doubt, use tag Rel_2_2_1, we can later rename
> it to JBoss_2_2_1_Final. CVS tags are very easy to add, delete, rename, etc,
> so better tag once more than once less.
>
> If a release is needed, you can now package everything again and upload to
> the web site (Oh, if someone finds the time, update also the main page that
> still refers to Rickard's 2.1 (beta) release, and maybe moving it in a more
> visible position, like at the top of the main page)
>
> Update also the main trunk:
> cvs up -A
>
> Change again the files (on this new working copy from the main trunk)
> applying the patch (or if you know well CVS you can merge the changes) and
> commit the changes.
>
> Hope helps, but if you have doubts don't hesitate to contact me.
>
> Cheers,
>
> Simon
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
