NOTE: anyone who currently has a checked-out copy of RELEASE_0_38_0, the tags in your working copy are most likely hosed; please check out a fresh copy!
Since we need to do a point release, I went to check out the 0.38 release branch, only to discover that there wasn't one -- and RELEASE_0_38_0 was a branch tag itself.
That's a problem, because I can't just check out RELEASE_0_38_0, commit the point fixes, and tag RELEASE_0_38_1 -- it would have moved the head of the branch and the next person to check out RELEASE_0_38_0 would have gotten something other than our 0.38(.0) release...
In future, PLEASE do this:
RELEASE_0_X_BRANCH - a branch for the 0.X.Y releases
RELEASE_0_X_Y - a regular tag for the
That way, if we need to do a point release, we can just check out RELEASE_0_X_BRANCH, commit the fixes, and tag RELEASE_0_X_Y; no muss, no fuss.
As noted at the top of the email I have moved and rebranched the existing 0.38 tag accordingly. RELEASE_0_38_0 is now a regular tag, and RELEASE_0_38_BRANCH is now the branch tag.
-mental
Can you doublecheck our CreatingDists documentation and update it to be consistent with the correct process?
http://www.inkscape.org/cgi-bin/wiki.pl?CreatingDists
Bryce
On Thu, 8 Apr 2004, MenTaLguY wrote:
NOTE: anyone who currently has a checked-out copy of RELEASE_0_38_0, the tags in your working copy are most likely hosed; please check out a fresh copy!
Since we need to do a point release, I went to check out the 0.38 release branch, only to discover that there wasn't one -- and RELEASE_0_38_0 was a branch tag itself.
That's a problem, because I can't just check out RELEASE_0_38_0, commit the point fixes, and tag RELEASE_0_38_1 -- it would have moved the head of the branch and the next person to check out RELEASE_0_38_0 would have gotten something other than our 0.38(.0) release...
In future, PLEASE do this:
RELEASE_0_X_BRANCH - a branch for the 0.X.Y releases
RELEASE_0_X_Y - a regular tag for the
That way, if we need to do a point release, we can just check out RELEASE_0_X_BRANCH, commit the fixes, and tag RELEASE_0_X_Y; no muss, no fuss.
As noted at the top of the email I have moved and rebranched the existing 0.38 tag accordingly. RELEASE_0_38_0 is now a regular tag, and RELEASE_0_38_BRANCH is now the branch tag.
-mental
On Fri, 2004-04-09 at 01:12, Bryce Harrington wrote:
Can you doublecheck our CreatingDists documentation and update it to be consistent with the correct process?
http://www.inkscape.org/cgi-bin/wiki.pl?CreatingDists
Nathan, could you also please update this page with instructions for updating the debian/ directory (manually, without using any of the debian tools, since the person doing it won't necessarily have debian)?
-mental
MenTaLguY wrote:
On Fri, 2004-04-09 at 01:12, Bryce Harrington wrote:
Can you doublecheck our CreatingDists documentation and update it to be consistent with the correct process?
Nathan, could you also please update this page with instructions for updating the debian/ directory (manually, without using any of the debian tools, since the person doing it won't necessarily have debian)?
The only thing omitted in this release was updating the changelog. I've updated it for the debs on sf, and the cvs head has the corrected files. It's certainly not worth making another release.
wiki updated.
njh
MenTaLguY wrote:
That's a problem, because I can't just check out RELEASE_0_38_0, commit the point fixes, and tag RELEASE_0_38_1 -- it would have moved the head of the branch and the next person to check out RELEASE_0_38_0 would have gotten something other than our 0.38(.0) release...
Obligatory Subversion mention......
Just kidding! ;-)
Bob
participants (4)
-
Bob Jamison -
Bryce Harrington -
MenTaLguY -
Nathan Hurst