SDCC 3.7.0 Release Plan

From SDCC wiki
Jump to: navigation, search

Contents

Release manager

?

Target platforms

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

  • Microsoft Windows 2000 and above (win32) x86
  • Microsoft Windows Vista and above (win64) amd64
  • glibc based Linux (linux) x86
  • macOS (darwin) amd64

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

Processor targets

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 maintenance: mcs51, ds390, z80, z180, r2k, r3ka, gbz80, hc08, s08 and stm8.
  • Preliminary, in development: pic14, pic16 and tlcs90.
  • Unknown status: TININative, ds400.
  • No longer maintained: avr.

Deliverables

The final deliverables will be:

  • A source archive that can rebuild all binaries
  • A documentation archive
  • 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

Acceptance criteria

  • Have an updated README
  • Shall compile without errors on at least GNU/Linux (amd64), GNU/Linux (x86), macOS (amd64) and Windows (amd64).
  • Should compile without errors on at least Windows (x86), NetBSD (x86) and Solaris (sparc).
  • Pass regression tests on all "Mature" targets (mcs51, ds390, z80, z180, r2k, r3ka, tlcs90, gbz80, hc08, s08 and stm8) on Linux, Windows, Mac OS X, NetBSD and Solaris.

Schedule

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

The schedule and approximate timings are:

  1. Announce intention to do a release ?
  2. Take feedback and wish list items ?
  3. Change the version number in .version, sdcc.spec, doc/INSTALL.txt and everywhere else it appears ?
  4. Announce a code freeze ?
    1. The release candidate RC1 svn tag will be created. NOTE: the tag should be created on a complete sdcc trunk: http://svn.code.sf.net/p/sdcc/code/trunk ?
    2. The release manager will make a release candidate RC1 ?
    3. RC1 deliverables will be released to the staging area so that people can test the installers. ?
    4. Update the NEWS section of sdcc-web/index.php: move previous release to Past News and add RC1 to News. ?
    5. Bugs (packaging, documentation, ...) found in RC1 will be fixed ?
    6. The release candidate RC2 svn tag will be created. NOTE: the tag should be created on a complete sdcc trunk: http://svn.code.sf.net/p/sdcc/code/trunk ?
    7. The release manager will make a release candidate RC2 ?
    8. RC2 deliverables will be released to the staging area so that people can test the installers. ?
    9. Update the NEWS section of sdcc-web/index.php: add RC2 to News. ?
    10. Bugs (packaging, documentation, ...) found in RC2 will be fixed ?
  5. The release svn tag will be created. NOTE: the tag should be created on a complete sdcc trunk: http://svn.code.sf.net/p/sdcc/code/trunk ?
  6. The release manager will make the release deliverables. ?
  7. Quick test of the installers ?
  8. Deliverables will be blessed and released ?
  9. Mark the new files as default download for their operating system. ?
  10. Update the NEWS section of sdcc-web/index.php: move previous release to previous.php, move RC news to Past News and add new release to News. ?
  11. The release will be announced on SourceForge News, sdcc-devel and sdcc-user mailing lists ?

Tasks

Random set of tasks that someone might want to do:

  • Update the web page before and after the release
  • Update the documentation
  • Announce the release elsewhere (e.g. hardware vendor forums)
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox