Releases...
Normally, when I do releases I make two tags. For the past 20 or so
releases, they are at the exact same place. Since I am a little stuck in
thinking CVS and at the same time I would like to attempt at simplify
the procedure, I am thinking that we could use the tags like this.
I take all the release tags, the ones named like VERSION_0_21_3 and put
them in the releases directory (a new one that works a little like the
tags directory and a little like the branches directory). I can remove
all the freeze tags (the ones named like VERSION_0_21_3_F).
For upcoming releases I start by setting the "tag" (creating a new "tag"
like VERSION_0_21_3) in the releases directory and then I do the release
work there. If the release fails, I just make the change in the
releases/VERSION_0_21_3 copy and finish the release work. If we shall do
another release based on that release we will then take the
releases/VERSION_0_21_3, make a branch in branches/BRANCH_0_21_3 and
when completed copy that one to releases/VERSION_0_21_3_1 or whatever
the new name is. The purpose of this is that we shall never change the
releases/VERSION_0_21_3 subdirectory once the release is out.
Is this a good idea or should I do it in some other way.
I plan to apply the same procedure over all argouml projects that are
included in the release.
/Linus
*******************************************************************
Linus Tolke
[EMAIL PROTECTED]
*******************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
