SDCC 2.7.0 Release Plan - roybaer/sdcc-wiki GitHub Wiki

Table of Contents Release manager Target platforms Processor targets Deliverables Acceptance criteria Schedule Tasks

Borut Razem

SDCC binaries will be built for the following platforms, called also "official SDCC platforms":

• Microsoft Windows 2000 and above (win32) 32bit x86

 It is known that [http://sourceforge.net/tracker/index.php?func=detail&aid=1631528&group_id=599&atid=100599 SDCC Hangs on Win98 SE], but we can't fix it due to lack of the platform :-(

• glibc based Linux (linux) 32bit x86
• Mac OS X 10.4.8 (darwin) 32bit PPC

gcc and command line tools will be used to build ports on all platforms. Windows port will be cross-compiled on Linux host.

Some targets are not ready or are no longer maintained. Any mature targets must be included and must pass the regression tests. Any others may be disabled in the binary to meet the acceptance criteria.

• Mature, on-going maintanance: mcs51, ds390, z80 and hc08
• Preliminary, in development: pic14, pic16
• No longer maintained: avr, gbz80
• Unknown status: TININative, xa51, ds400

The final deliverables will be:

• A source archive that can rebuild all binaries
• An executable, NSIS based installer for Windows
• A tarball that installs in /usr/local for Linux
• A tarball that installs in /Developer/SDCC for Mac OS X

The release needs to at minimum:

• Have an updated README
• Compile without warnings or errors on all platforms
• Pass regression tests on all "Mature" targets: mcs51, ds390, z80 and hc08 on Linux, Windows and Mac OS X

This schedule has no dates attached due to the volunteer nature of the project, however Borut will try to keep things moving.

The schedule and approximate timings are:

1. Announce intention to do a release (DONE 2007-03-31)
2. Take feedback and wish list items (DONE)
3. Announce a code freeze (DONE 2007-05-10)
   1. Change the version number in .version, sdcc.spec, doc/sdccman.lyx and everywhere else it appears (DONE 2007-05-08)
   2. Regenerate doc/knownbugs.html with support/scripts/gen_known_bugs.pl for the release candidate RC1 (DONE 2007-05-10)
   3. The release candidate RC1 svn tag will be created (DONE 2007-05-10)
   4. The release manager will make a release candidate RC1 (DONE 2007-05-10)
   5. RC1 deliverables will be released to the staging area so that people can test the installers. (DONE 2007-05-10)
   6. Bugs (packaging, documentation, ...) found in RC1 will be fixed (DONE)
   7. Regenerate doc/knownbugs.html with support/scripts/gen_known_bugs.pl for the release candidate RC2 (DONE 2007-05-22)
   8. The release candidate RC2 svn tag will be created (DONE 2007-05-22)
   9. The release manager will make a release candidate RC2 (DONE 2007-05-22)
   10. RC2 deliverables will be released to the staging area so that people can test the installers. (DONE 2007-05-22)
   11. Regenerate doc/knownbugs.html with support/scripts/gen_known_bugs.pl for the release candidate RC3 (DONE 2007-05-26)
   12. The release candidate RC3 svn tag will be created (DONE 2007-05-26)
   13. The release manager will make a release candidate RC3 (DONE 2007-05-26)
   14. RC3 deliverables will be released to the staging area so that people can test the installers. (DONE 2007-05-26)
4. Regenerate doc/knownbugs.html with support/scripts/gen_known_bugs.pl (DONE)
5. The release svn tag will be created (DONE 2007-05-31)
6. The release manager will make the release deliverables (DONE 2007-05-31)
7. Quick test of the installers (DONE 2007-05-31)
8. Deliverables will be blessed and released (DONE 2007-05-31)
9. Change the version number again in .version, sdcc.spec, doc/sdccman.lyx and everywhere else it appears (DONE 2007-05-31)
10. The release will be announced on SourceForge News, sdcc-devel and sdcc-user mailing lists (DONE 2007-05-31)

Random set of tasks that someone might want to do:

• Update the web page before and after the release (DONE 2007-05-31)
• Update the documentation (DONE 2007-05-31)