Re: stable/2.12 and tagging of tarballs

[Jan Nieuwenhuizen]

Op maandag 08-06-2009 om 17:12 uur [tijdzone +0200], schreef Jan
Nieuwenhuizen:

> As it turns out after discussing with Han-Wen, it seems that
> 2.12.2 was released from MASTER after stable/2.12 was branched.
> Don't ever do that! ;-)

Looking further into this, I found that our lilypond-2.12.2 tarball
  
    http://lilypond.org/download/source/v2.12/lilypond-2.12.2.tar.gz

does *not* match git's release/2.12.2-1 tag.  

Sadly, GUB does not produce source tarballs by default, because we 
assume the build process to be fail safe.  So, possibly this is a GUB
bug/glitch/loophole, Han-Wen?

The difference is minor

    diff -purN --exclude=out --exclude=out-www --exclude=.git 
--exclude-from=.gitignore --exclude=autogen.sh --exclude=NEWS.txt 
--exclude=README.txt ./Documentation/GNUmakefile 
/home/janneke/vc/lilypond-2.12/Documentation/GNUmakefile
    --- ./Documentation/GNUmakefile     2009-01-20 13:31:56.000000000 +0100
    +++ /home/janneke/vc/lilypond-2.12/Documentation/GNUmakefile        
2009-06-08 17:02:58.203202085 +0200
    @@ -2,8 +2,7 @@ depth = ..

     NAME = documentation
     LANGS = $(shell $(PYTHON) $(top-src-dir)/python/langdefs.py)
    -# Dist JA separately, because the doc-compile does not work yet.
    -SUBDIRS=devel user bibliography pictures topdocs misc po $(LANGS) ja
    +SUBDIRS=devel user bibliography pictures topdocs misc po $(LANGS)
     STEPMAKE_TEMPLATES=documentation texinfo tex
     LOCALSTEPMAKE_TEMPLATES=lilypond ly
     LILYPOND_BOOK_FLAGS=--extra-options '-e "(ly:set-option (quote 
internal-type-checking) \#t)"'
    diff -purN --exclude=out --exclude=out-www --exclude=.git 
--exclude-from=.gitignore --exclude=autogen.sh --exclude=NEWS.txt 
--exclude=README.txt ./Documentation/ja/GNUmakefile 
/home/janneke/vc/lilypond-2.12/Documentation/ja/GNUmakefile
    --- ./Documentation/ja/GNUmakefile  2009-01-21 05:35:10.000000000 +0100
    +++ /home/janneke/vc/lilypond-2.12/Documentation/ja/GNUmakefile     
2009-06-08 16:02:13.119204652 +0200
    @@ -2,6 +2,6 @@ ISOLANG = ja
     depth = ../..
     SUBDIRS = user
     STEPMAKE_TEMPLATES = documentation
    -LOCALSTEPMAKE_TEMPLATES = # doc-i18n-root
    +LOCALSTEPMAKE_TEMPLATES = doc-i18n-root

     include $(depth)/make/stepmake.make
    diff -purN --exclude=out --exclude=out-www --exclude=.git 
--exclude-from=.gitignore --exclude=autogen.sh --exclude=NEWS.txt 
--exclude=README.txt ./GNUmakefile /home/janneke/vc/lilypond-2.12/GNUmakefile

but at least now I understand why the GUB binaries built fine,
but packagers must patch out the JA translation to get it to build.

I wonder why a new japanese translation was added to stable
development, or to put it differently...

> Also, I have regenerated the stable/2.12 branch.

... the stable branch that I now recreated, from master
at tag release/2.12.2-1, *was* that actually bugfixing,
cautious development?
Or does our 2.12.2 release include new, risky development?

Also, as nothing had been committed to the stable branch
for the past half year I wonder: have absolutely no bugs
been fixed since 2.12.2?  Did some major change prevent
fixes from being backported?

I suppose some small kind of pond creature should look over
the master branch since release/2.12.2-1 to see if any commits
can/should be added to stable/2.12 before we release 2.12.3?

Or did we have no/little unstable development, and should
MASTER be renamed to stable/2.12?

Greetings,
Jan.

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
Avatar®: http://AvatarAcademy.nl    | http://lilypond.org