Difference between revisions of "Release 2.2.2"
From Lazarus wiki
Jump to navigationJump to searchLine 7: | Line 7: | ||
# Agree on deadline for changes and date for release candidate building | # Agree on deadline for changes and date for release candidate building | ||
− | ## | + | ## [[Release_2.2.2#2.2.2_-_RC_1]] deadline : June 8<sup>th</sup>, 2008 |
− | ## | + | ## [[Release_2.2.2#2.2.2_-_RC_2]] deadline : |
## do we need extra RC? | ## do we need extra RC? | ||
## Final release deadline | ## Final release deadline |
Revision as of 23:31, 19 May 2008
Release Issues
The issues page is Issues 2.2.2
Release preparations
- Agree on deadline for changes and date for release candidate building
- Release_2.2.2#2.2.2_-_RC_1 deadline : June 8th, 2008
- Release_2.2.2#2.2.2_-_RC_2 deadline :
- do we need extra RC?
- Final release deadline
- Check the Detailed 2.2.2 Todo page (should be linked from To Do lists) for status of individual todo items
- Check status of bugs assigned to that particular release in the bugtracker
New page in Wiki named "Release_2.2.2" for release procedure with steps needed and their status (based on Release Template), at the beginning consisting of (at least) RC1 and final release sections- Ask platform maintainers and external maintainers about including their platforms/builds in the new release
- Release-like building procedure should be performed in the appropriate branch (trunk or fixes depending on basis for the release)
- Check and update all .msg files
- errore.msg
- errord.msg
- errorf.msg
- errorn.msg
- errorr.msg
- errorrw.msg
- errorues.msg
- errores.msg
- errorct.msg
- errorhe.msg
- errorheu.msg
- errorptd.msg
- errorptw.msg
- errorpli.msg
- errorpl.msg
- errorid.msg
- Check tools
- Check version of the above mentioned tools (GNU tools, helper DLLs, UPX, etc.), and decide whether it isn't time to update some of these tools
- Repackage and upload additional tools where needed
- Update whatsnew.txt (/install/doc/whatsnew.txt)
- Find testers
- Create a page in Wiki ("Testers_X.Y.Z" based on Testers Template)
- Ask in fpc-devel list for volunteers interested in testing the individual platforms / builds and list them on the newly created page (they can add themselves)
- Finish all source file updates
- Update version number to new release number
- /install/doc/readme.txt
- /installer/install.dat (header)
- /installer/install.pas (installer version)
- /install/fpc.spec
- convert /html/faq.fp to /install/doc/faq.htm and /install/doc/faq.txt
- /docs/fpc.sty (macro fpcversion)
- All Makefile.fpc files containing version=... (plus regenerate all corresponding Makefiles)
2.2.2 - RC 1
- RC1 deadlines
- Code freeze : May 31th, 2008 at 00:00:00
- Build verification : during next week until June 6th June, 2008 at 00:00:00
- Tag creation : June 7th, 2008 at 12:00:00
- Build and upload end : June 8th, 2008 at 23:00:00
- Mailing list announcement : June 8th, 2008 at 23:50:00
Create new page in Wiki with issue log for documentation of issues encountered in release candidates and their status ("Issues_X.Y.Z" based on Issues Template)- New directories
- Create new directories on ftp (/pub/fpc/beta/X.Y.Z-rcN and cpu-os under that)
- Copy the extra files (asld*.zip, gdb*.zip, make*.zip) from previous release (unless updated with new versions)
- Add new section for the upcoming build in /install/debian/changelog
- Create new rc branch in SVN (release_X_Y_Z_rcN)
- Update version number in rc branch to X.Y.Z-rcN
- /compiler/version.pas
- Create and upload exported fpcbuild
- fpcbuild-%{version}.zip
- fpcbuild-%{version}.tar.gz
- Create and upload the documentation (more info)
- doc-pdf.zip
- doc-html.zip
- doc-htm.zip (not included)
- doc-txt.zip
- doc-ps.zip
- doc-pdf.tar.gz
- doc-html.tar.gz
- doc-ps.tar.gz
- Create and upload source zips
- short name version for binary packages
- docs source (including link for short name version)
- long name version for binary packages
- Create and upload zip files for i386-go32v2
- basic zip (just binaries)
- full zip (including docs and sources)
- Create and upload zip files for i386-os2
- basic zip (just binaries)
- full zip (including docs and sources)
- Create and upload installer exe for i386-win32
- Create and upload tgz file for i386-freebsd
- Create and upload release for i386-linux (more info)
- tar
- deb (Mazen)
- rpm
- Create and upload release for powerpc-linux (more info)
- tar
- Create and upload release for powerpc-macosx
- .dmg package
- .info files for fink
- Build and upload bootstrapcompiler
- Update paths, file names and MD5sums, ... in /install/macosx/*.info for the new RC
- Create and upload release for i386-macosx
- .dmg package
- .info files for fink (see powerpc-macosx)
- Create and upload release for powerpc-macos
- Create and upload release for powerpc-morphos
- Create and upload release for powerpc-amiga
- Create and upload zip files for i386-netware
- Create and upload zip files for i386-netwlibc
- Create and upload release for sparc-linux (more info)
- tar
- deb (Mazen)
- Create and upload release for sparc-sunos
- tar
- Create and upload release for arm-linux (cross-release)
- tar
- Create and upload release for x86_64-linux (more info)
- tar
- deb
- rpm
- Get it tested
- Ask dedicated testers for testing their platforms
- Consider announcing availability of the new RC in fpc-devel list
- Test the GO32v2 release
- dos???.zip installation
- dos???full.zip installation (over the previously installed dos???.zip to simulate updates)
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/go32v2 (no params)
- make cycle with newly installed binaries and sources
- run testsuite
- open the installed hello.pp in IDE
- make a minor change in the demo in IDE & save it
- view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
- compile the demo file in IDE
- run the demo within the IDE (debugger)
- Test the OS/2 release
- os2???.zip installation
- os2???full.zip installation (over the previously installed os2???.zip to simulate updates)
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/os2 (no params)
- make cycle with newly installed binaries and sources
- run testsuite
- open the installed hello.pp in IDE
- make a minor change in the demo in IDE & save it
- view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
- compile the demo file in IDE
- run the demo within the IDE (debugger) (not supported)
- Test the Win32 release
- Run installer
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/win32 (without parameters)
- make cycle with newly installed binaries and sources
- run testsuite
- open the installed hello.pp in IDE
- make a minor change in the demo in IDE & save it
- view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
- compile the demo file in IDE
- run the demo within the IDE (debugger)
- Test release for i386-freebsd
- Test release for i386-linux
- tar
- deb (Mazen)
- rpm
- Test release for powerpc-linux
- tar
- Test release for powerpc-macosx
- .dmg package
- .info file for fink
- Test release for i386-macosx
- .dmg package
- .info file for fink
- Test release for powerpc-macos
- Test release for powerpc-morphos
- Test release for powerpc-amiga
- Test release for i386-netware
- Test release for i386-netwlibc
- Test release for sparc-linux
- tar
- deb (Mazen)
- Test release for arm-linux
- tar
- Test release for x86_64-linux
- tar
- deb
- rpm
- Check PDF documentation (open all files)
- Check HTML documentation
- Check TXT documentation
- Read updated text files as distributed in release zip files
- readme.txt
- faq.txt
- whatsnew.txt
RC2
- Section for new RC on release pages in Wiki
- Release procedure
- Issue log
- Look at unmerged changes in fpc and fpcbuild since the last RC and consider/ask for necessity of their inclusion in the release
- New directories
. .
Final release
- Look at unmerged changes in fpc and fpcbuild since the last RC and consider/ask for necessity of their inclusion in the release (only cosmetic changes should be included, otherwise a new RC is needed instead of final release)
- New directories
- Create new directories on ftp (/pub/fpc/dist/cpu-os-X.Y.Z)
- Copy the extra files (asld*.zip, gdb*.zip, make*.zip) from previous RC (unless updated with new versions)
- Add new section for the upcoming build in /install/debian/changelog
- Create new release branch in SVN
- Update version number in release branch to the X.Y.Z
- /compiler/version.pas
- Create and upload exported fpcbuild
- fpcbuild-%{version}.zip
- fpcbuild-%{version}.tar.gz
- Create and upload the documentation (more info)
- doc-pdf.zip
- doc-html.zip
- doc-htm.zip (not included)
- doc-txt.zip
- doc-ps.zip
- doc-pdf.tar.gz
- doc-html.tar.gz
- doc-ps.tar.gz
- Create and upload source zips
- short name version for binary packages
- docs source (including link for short name version)
- long name version for binary packages
- Create and upload zip files for i386-go32v2
- basic zip (just binaries)
- full zip (including docs and sources)
- Create and upload zip files for i386-os2
- basic zip (just binaries)
- full zip (including docs and sources)
- Create and upload installer exe for i386-win32
- Create and upload tgz file for i386-freebsd
- Create and upload release for i386-linux (more info)
- tar
- deb
- rpm
- Create and upload release for powerpc-linux (more info)
- tar
- Create and upload release for powerpc-macosx
- .dmg package
- .info files for fink
- Build and upload bootstrapcompiler
- Update paths, file names and MD5sums, ... in /install/macosx/*.info for the new RC
- Create and upload release for i386-macosx
- .dmg package
- .info files for fink (see powerpc-macosx)
- Create and upload release for powerpc-macos
- Create and upload release for powerpc-morphos
- Create and upload release for powerpc-amiga
- Create and upload zip files for i386-netware
- Create and upload zip files for i386-netwlibc
- Create and upload release for sparc-linux (more info)
- tar
- Create and upload release for arm-linux (cross-release)
- tar - Daniel
- Create and upload release for x86_64-linux (more info)
- tar
- deb
- rpm
- Test the GO32v2 release
- dos???.zip installation
- dos???full.zip installation (over the previously installed dos???.zip to simulate updates)
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/go32v2 (no params)
- make cycle with newly installed binaries and sources
- run testsuite
- open the installed hello.pp in IDE
- make a minor change in the demo in IDE & save it
- view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
- compile the demo file in IDE
- run the demo within the IDE (debugger) (debugging in IDE currently not available/working)
- Test the OS/2 release
- os2???.zip installation
- os2???full.zip installation (over the previously installed os2???.zip to simulate updates)
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/os2 (no params)
- make cycle with newly installed binaries and sources
- run testsuite
- open the installed hello.pp in IDE
- make a minor change in the demo in IDE & save it
- view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
- compile the demo file in IDE
- run the demo within the IDE (debugger) (not supported)
- Test the Win32 release
- Run installer
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/win32 (without parameters)
- make cycle with newly installed binaries and sources
- run testsuite
- open the installed hello.pp in IDE
- make a minor change in the demo in IDE & save it
- view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
- compile the demo file in IDE
- run the demo within the IDE (debugger)
- Test release for i386-freebsd
- Test release for i386-linux
- tar
- deb
- rpm
- Test release for powerpc-linux
- tar
- Test release for powerpc-macosx
- .dmg package
- .info file for fink
- Test release for i386-macosx
- .dmg package
- .info file for fink
- Test release for powerpc-macos
- Test release for powerpc-morphos
- Test release for powerpc-amiga
- Test release for i386-netware
- Test release for i386-netwlibc
- Test release for sparc-linux
- tar
- Test release for arm-linux
- tar
- Test release for x86_64-linux
- tar
- deb
- rpm
- Check PDF documentation (open all files)
- Check HTML documentation
- Check TXT documentation
- Read updated text files as distributed in release zip files
- readme.txt
- faq.txt
- whatsnew.txt
Going public
- Make new version numbers (release plus next odd patch number for continuing fixes) available in bug tracker
- Make new version numbers (release plus next odd patch number for continuing fixes) available in testsuite db
- Make new files on FTP available to wide public
- update symlinks (no symlinks any more?)
- move the old version to the olddist/<version>
- upload files to SourceForge.net and add them to new "releases" for individual platforms
- make new "releases" on SourceForge.net accessible for users (change status to "active")
- Allow automated notifications on individual SourceForge.net file release pages to be sent
- Submit darwin packages to fink
- Update WWW pages
- /html/news.fp
- /html/down/* (links to all individual files & file sizes)
- /html/download.fp (version number and list of platforms)
- /html/fpc.fp
- /html/faq.fp (things like "the latest version is ...")
- Create new fixes branch (only after a major release - ?.?.0)
- Update version number in the trunk branch (only after a major release - ?.?.0)
- /compiler/version.pas
- All Makefile.fpc files containing "version=..." (plus regenerate the corresponding Makefiles)
- Update version number in the trunk branch (only after a major release - ?.?.0)
- Update version number in the fixes branch (increase the patch to next odd number)
- /compiler/version.pas
- all Makefile.fpc files containing "version=..." (plus regenerate the corresponding Makefiles)
- Check the WWW pages
- make sure http://www.freepascal.org contains the new version already
- read news.html
- read fpc.html
- read download.html and check links to individual files
- Send announcement to our mailing lists
- Post announcement on the community site
- Post announcement on Sourceforge.net (only "Project Administrators" may do it)
- Make sure that all unfixed issues encountered during RC testing and listed on dedicated page in Wiki are documented in bug tracker too
- Revise / update /html/future.fp after major versions (?.?.0)
- Remove unneeded RC builds from FTP