<Untitled> (54 items)
----------

 #   -  do s/solfege0.7/solfege1.0/ before the stable release.
 #   -  send bug til bug-texinfo@gnu.org om at vi ikke kan ha en @email i
        en @subsection, men at@code fungerer
[+]  -  Most important TODOs
 #   -  If no new problems are reported, only lesson files, documentation
        and translations (and the /dev/sequencer percussion fix) will be
        added before the 1.0 release.
 #   -  er det mulig  f opp en messagebox hvis vi har angitt en
        midiplayer som ikke finnes?
 #   -  jeg distribuerer .mo filer. Skal dette gjres?
[-]  -  Packaging
    [-]  -  Debian
         #   -  When 1.0 is released and I start 1.1.x, files should be
                installed into /usr/share/solfege1.1/ and
                /usr/lib/solfege1.1/ so we can have both the stable and
                unstable release installed.
                
                When 1.2 is released we release that as package solfege,
                with
                Replaces: solfege1.1
                Conlicts: solfege1.1
                (Ask on debian-mentors to check that this is correct
                procedure)
         #   -  Apps/Educational menu policy??
         #   -  debian-menu: Education/Music
         #   -  should probably depend on python, not python-base
         #   -  To get correct built package with diff file, in the dir
                where I unpacked the released tarball, I copy
                solfege-x.y.z.tar.gz to solfege_x.y.z.orig.tar.gz
                
                This way, I can make solfege_x.y.z-2 release with only
                .diff upload, no new tar.gz source
     #   -  Rpm: packages built on clean RH 6.2 and 7.0, mandrake etc...
            Someone with just a little clue can do this. Just make sure you
            have a clean system, and do "make rpm"
[+]  -  misc TODO
[+]  -  Bugs
[+]  -  Tasks without programming skills
[+]  -  Stuff to remember
[+]  -  Thoughts about new exercises
[+]  -  TODO and plans for 1.1.x

---=== end <Untitled> ===---
