1.6.8 - because the 1.6.8 branch (read: svn tag) seems to be made from
a wc with local changes. This is the diff from where I really want to
place the tag:
diff --git a/ANNOUNCE b/ANNOUNCE
index f5276aa..d8c87f7 100644
--- a/ANNOUNCE
+++ b/ANNOUNCE
@@ -70,9 +70,6 @@ want to apply one of the following patches instead:
ftp://ftp.lyx.org/pub/lyx/stable/1.6.x/patch-1.6.8.gz
ftp://ftp.lyx.org/pub/lyx/stable/1.6.x/patch-1.6.8.bz2
-Note that for this release, some binaries have been added that are not produced
-by the patch.
-
If you find what you think is a bug in LyX 1.6.8, you may either
e-mail the LyX developers' mailing list (lyx-devel<at> lists.lyx.org),
or open a bug report at http://www.lyx.org/trac/
I am inclined to ignore this difference and place the tag in the best
spot, instead of where it would be "correct". The diff above will then
added in the next commit after the 1.6.8 tag.
The difference is really minor, so it would not be a problem.
To me it seems that the correct thing to do is to split 58c867b (r36302)
and to put the tag on the commit that contains the change in ANNOUNCE.
Any reasons not to do so ?
1.4.0pre5 is also problematic. Created from a mixed revision wc it
seems. (I wonder how cvs made that happen...)
I don't know where 1.4.0pre5 should be, but if it is a mixed revision,
isn't it possible to also split this revision ?
I am inclined to put the tag in the "best" spot. Will be a bit unice in
that if you build from the tag the the resulting binary will not call
itself 1.4.0pre5 but 1.4.0svn.
To correct this, we probably need to change the history. Is this
ethically ok to do ? I think we can, albeit for cosmetical reasons.
Similar with 1.4.0pre6.
And with 1.4.0 as well, this is especially bad. It might be possible to
fixup this with grafting, not sure if it is worth the effort though.
I have the feeling, it wouldn't be that difficult to fix it.
Current list of tags:
1.1.1
1.1.1pre2
1.1.2
1.1.3
1.1.4
1.1.5
1.1.5fix1
1.1.5fix2
1.1.5pre1
1.1.5pre2
1.1.5pre3
1.1.6
1.1.6fix1
1.1.6fix2
1.1.6fix3
1.1.6fix4
1.1.6pre1
1.1.6pre2
1.1.6pre3
1.2.0
1.2.0pre1
1.2.0pre2
1.2.0pre3
1.2.0pre4
1.2.0pre5
1.2.0rc1
1.2.1
1.2.2
1.2.3
1.3.0
1.3.0pre1
1.3.0pre2
1.3.0pre3
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.4.0pre1
1.4.0pre2
1.4.0pre3
1.4.0pre4
1.4.0pre5
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
1.4.5.1
1.5.0
1.5.0alpha1
1.5.0rc2
1.5.0alpha2
1.5.0rc1
.. are still missing.
Vincent