SDCC 3.3.0 Release Plan - Revision history

MaartenBrock: /* Schedule */

2013-05-19T23:10:16Z

‎Schedule

MaartenBrock: /* Schedule */

2013-05-19T23:07:36Z

‎Schedule

MaartenBrock: /* Schedule */

2013-05-18T13:02:31Z

‎Schedule

MaartenBrock: /* Schedule */

2013-05-11T21:18:30Z

‎Schedule

MaartenBrock: /* Schedule */

2013-05-10T21:23:45Z

‎Schedule

MaartenBrock: /* Schedule */

2013-05-05T14:31:10Z

‎Schedule

MaartenBrock: /* Schedule */

2013-05-04T13:47:01Z

‎Schedule

MaartenBrock: /* Schedule */

2013-05-04T12:34:02Z

‎Schedule

MaartenBrock: /* Release manager */

2013-05-03T13:07:17Z

‎Release manager

Borutr at 21:48, 4 December 2012

2012-12-04T21:48:46Z

New page

== Release manager ==
Not defined yet.

== Target platforms ==
SDCC binaries will be built for the following platforms, called also "official SDCC platforms":
*Microsoft Windows 2000 and above (win32) 32bit x86
It is was reported that [http://sourceforge.net/tracker/index.php?func=detail&aid=1631528&group_id=599&atid=100599 SDCC Hangs on Win98 SE], but I [borutr] couldn't reproduce it.
This means that SDCC runs on Windows 95/98/ME platforms too, but they are not officially supported.
*glibc based Linux (linux) 32bit x86
*Mac OS X (darwin) 32bit ppc and i386 universal binaries

gcc and command line tools will be used to build ports on all platforms. Windows port 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 and s08.
*Preliminary, in development: pic14, pic16
*Unknown status: TININative, ds400
*No longer maintained: avr, xa51

== 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 ==
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, z180, r2k, r3ka, gbz80, hc08 and s08 on Linux, Windows and Mac OS X

== 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:
#Announce intention to do a release
#Take feedback and wish list items
#Change the version number in .version, sdcc.spec, doc/sdccman.lyx, doc/INSTALL.txt and everywhere else it appears
#Announce a code freeze
##The release candidate RC1 svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk''
##The release manager will make a release candidate RC1
##RC1 deliverables will be released to the staging area so that people can test the installers.
##Bugs (packaging, documentation, ...) found in RC1 will be fixed
##The release candidate RC2 svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk''
##The release manager will make a release candidate RC2
##RC2 deliverables will be released to the staging area so that people can test the installers.
##Bugs (packaging, documentation, ...) found in RC2 will be fixed
#The release svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk''
#The release manager will make the release deliverables
#Quick test of the installers
#Deliverables will be blessed and released'
#The release will be announced on [http://sourceforge.net/news/?group_id=599 SourceForge News], [mailto:sdcc-devel@lists.sourceforge.net sdcc-devel] and [mailto:sdcc-user@lists.sourceforge.net 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

@@ Line 54: / Line 54: @@
 #Quick test of the installers '''(DONE 2013-05-20)'''
 #Deliverables will be blessed and released '''(DONE 2013-05-20)'''
-#Mark the new files as default download for their operating system
+#Mark the new files as default download for their operating system '''(DONE 2013-05-20)'''
 #The release will be announced on [http://sourceforge.net/news/?group_id=599 SourceForge News], [mailto:sdcc-devel@lists.sourceforge.net sdcc-devel] and [mailto:sdcc-user@lists.sourceforge.net sdcc-user] mailing lists '''(DONE 2013-05-20)'''

@@ Line 49: / Line 49: @@
 ##The release manager will make a release candidate RC2 '''(DONE 2013-05-11)'''
 ##RC2 deliverables will be released to the staging area so that people can test the installers. '''(DONE 2013-05-11)'''
-##Bugs (packaging, documentation, ...) found in RC2 will be fixed
+##Bugs (packaging, documentation, ...) found in RC2 will be fixed '''(DONE 2013-05-18)'''
-#The release svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk''
+#The release svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk'' '''(DONE 2013-05-20)'''
-#The release manager will make the release deliverables
+#The release manager will make the release deliverables '''(DONE 2013-05-20)'''
-#Quick test of the installers
+#Quick test of the installers '''(DONE 2013-05-20)'''
-#Deliverables will be blessed and released
+#Deliverables will be blessed and released '''(DONE 2013-05-20)'''
 #Mark the new files as default download for their operating system
-#The release will be announced on [http://sourceforge.net/news/?group_id=599 SourceForge News], [mailto:sdcc-devel@lists.sourceforge.net sdcc-devel] and [mailto:sdcc-user@lists.sourceforge.net sdcc-user] mailing lists
+#The release will be announced on [http://sourceforge.net/news/?group_id=599 SourceForge News], [mailto:sdcc-devel@lists.sourceforge.net sdcc-devel] and [mailto:sdcc-user@lists.sourceforge.net sdcc-user] mailing lists '''(DONE 2013-05-20)'''
 == Tasks ==

@@ Line 47: / Line 47: @@
 ##Bugs (packaging, documentation, ...) found in RC1 will be fixed '''(DONE 2013-05-10)'''
 ##The release candidate RC2 svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk'' '''(DONE 2013-05-10)'''
-##The release manager will make a release candidate RC2
+##The release manager will make a release candidate RC2 '''(DONE 2013-05-11)'''
-##RC2 deliverables will be released to the staging area so that people can test the installers.
+##RC2 deliverables will be released to the staging area so that people can test the installers. '''(DONE 2013-05-11)'''
 ##Bugs (packaging, documentation, ...) found in RC2 will be fixed
 #The release svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk''

@@ Line 45: / Line 45: @@
 ##The release manager will make a release candidate RC1 '''(DONE 2013-05-05)'''
 ##RC1 deliverables will be released to the staging area so that people can test the installers. '''(DONE 2013-05-05)'''
-##Bugs (packaging, documentation, ...) found in RC1 will be fixed
+##Bugs (packaging, documentation, ...) found in RC1 will be fixed '''(DONE 2013-05-10)'''
-##The release candidate RC2 svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk''
+##The release candidate RC2 svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk'' '''(DONE 2013-05-10)'''
 ##The release manager will make a release candidate RC2
 ##RC2 deliverables will be released to the staging area so that people can test the installers.

@@ Line 43: / Line 43: @@
 #Announce a code freeze '''(DONE 2013-05-04)'''
 ##The release candidate RC1 svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk'' '''(DONE 2013-05-04)'''
-##The release manager will make a release candidate RC1
+##The release manager will make a release candidate RC1 '''(DONE 2013-05-05)'''
-##RC1 deliverables will be released to the staging area so that people can test the installers.
+##RC1 deliverables will be released to the staging area so that people can test the installers. '''(DONE 2013-05-05)'''
 ##Bugs (packaging, documentation, ...) found in RC1 will be fixed
 ##The release candidate RC2 svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk''

@@ Line 38: / Line 38: @@
 The schedule and approximate timings are:
-#Announce intention to do a release
+#Announce intention to do a release '''(DONE)'''
-#Take feedback and wish list items
+#Take feedback and wish list items '''(DONE)'''
-#Change the version number in .version, sdcc.spec, doc/sdccman.lyx, doc/INSTALL.txt and everywhere else it appears
+#Change the version number in .version, sdcc.spec, doc/sdccman.lyx, doc/INSTALL.txt and everywhere else it appears '''(DONE 2013-05-04)'''
 #Announce a code freeze
 ##The release candidate RC1 svn tag will be created. ''NOTE: the tag should be created on a complete sdcc trunk: https://sdcc.svn.sourceforge.net/svnroot/sdcc/trunk''

@@ Line 1: / Line 1: @@
 == Release manager ==
-Not defined yet.
+Maarten Brock
 == Target platforms ==