Release 2.2.2

From Lazarus wiki
Revision as of 10:58, 27 May 2008 by Michael (talk | contribs) (FPC-2.2.1-rc1)

Release Issues

The issues page is Issues 2.2.2

Release preparations

  1. Agree on deadline for changes and date for release candidate building
    1. #FPC-2.2.1-rc1 deadline : June 8th, 2008
    2. #FPC-2.2.1-rc2 deadline :
    3. do we need extra RC?
    4. #FPC-2.2.2 deadline
  2. Check the Detailed 2.2.2 Todo page (should be linked from To Do lists) for status of individual todo items
  3. Check status of bugs assigned to that particular release in the bugtracker
    • 10727 : Compiler : overloading problems involving literals.
    • 8076 : RTL : crt problem using gotoxy, write and SCREENWIDTH.
    • 10117 : Installer : fclel resource is not installed.
    • 11312 : Compiler : FPC doesn't generate far (32 bit) calls for sparc.
  4. 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
  5. Ask platform maintainers and external maintainers about including their platforms/builds in the new release
    1. Release-like building procedure should be performed in the appropriate branch (trunk or fixes depending on basis for the release)
  6. Check and update all .msg files
    1. errore.msg
    2. errord.msg
    3. errorf.msg
    4. errorn.msg
    5. errorr.msg
    6. errorrw.msg
    7. errorues.msg
    8. errores.msg
    9. errorct.msg
    10. errorhe.msg
    11. errorheu.msg
    12. errorptd.msg
    13. errorptw.msg
    14. errorpli.msg
    15. errorpl.msg
    16. errorid.msg
  7. Check tools
    1. 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
    2. Repackage and upload additional tools where needed
  8. Update whatsnew.txt (/install/doc/whatsnew.txt)
  9. Find testers
    1. Create a page in Wiki ("Testers_X.Y.Z" based on Testers Template)
    2. 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)
  10. Finish all source file updates
  11. Update version number to new release number
    1. /install/doc/readme.txt
    2. /installer/install.dat (header)
    3. /installer/install.pas (installer version)
    4. /install/fpc.spec
    5. convert /html/faq.fp to /install/doc/faq.htm and /install/doc/faq.txt
    6. /docs/fpc.sty (macro fpcversion)
    7. All Makefile.fpc files containing version=... (plus regenerate all corresponding Makefiles)

FPC-2.2.1-rc1

  1. Agree on 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
  2. 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)
  3. New directories
    1. Create new directories on ftp (/pub/fpc/beta/X.Y.Z-rcN and cpu-os under that)
    2. Copy the extra files (asld*.zip, gdb*.zip, make*.zip) from previous release (unless updated with new versions)
  4. Add new section for the upcoming build in /install/debian/changelog
  5. Create new rc branch in SVN (http://svn.freepascal.org/svn/fpcbuild/tags/release_2_2_1-rc1)
  6. Update version number in rc branch to X.Y.Z-rcN
    1. /compiler/version.pas
  7. Create and upload exported fpcbuild
    1. fpcbuild-%{version}.zip
    2. fpcbuild-%{version}.tar.gz
  8. Create and upload the documentation (more info) (michael)
    1. doc-pdf.zip
    2. doc-html.zip
    3. doc-htm.zip (not included)
    4. doc-txt.zip
    5. doc-ps.zip
    6. doc-pdf.tar.gz
    7. doc-html.tar.gz
    8. doc-ps.tar.gz
  9. Create and upload source zips
    1. short name version for binary packages
    2. docs source (including link for short name version)
    3. long name version for binary packages
  10. Create and upload zip files for i386-go32v2
    1. basic zip (just binaries)
    2. full zip (including docs and sources)
  11. Create and upload zip files for i386-os2
    1. basic zip (just binaries)
    2. full zip (including docs and sources)
  12. Create and upload installer exe for i386-win32
  13. Create and upload tgz file for i386-freebsd (Marcov)
  14. Create and upload release for i386-linux (more info)
    1. tar (Marcov)
    2. deb (Mazen)
    3. rpm
  15. Create and upload release for powerpc-linux (more info)
    1. tar (Thomas)
  16. Create and upload release for powerpc64-linux
    1. tar (Thomas)
  17. Create and upload release for powerpc-macosx
    1. .dmg package
    2. .info files for fink
      1. Build and upload bootstrapcompiler
      2. Update paths, file names and MD5sums, ... in /install/macosx/*.info for the new RC
  18. Create and upload release for i386-macosx
    1. .dmg package
    2. .info files for fink (see powerpc-macosx)
  19. Create and upload release for powerpc-macos
  20. Create and upload release for powerpc-morphos
  21. Create and upload release for powerpc-amiga
  22. Create and upload zip files for i386-netware
  23. Create and upload zip files for i386-netwlibc
  24. Create and upload release for sparc-linux (more info)
    1. tar
    2. deb (Mazen)
  25. Create and upload release for sparc-sunos
    1. tar
  26. Create and upload release for arm-linux (cross-release)
    1. tar
  27. Create and upload release for x86_64-linux (more info)
    1. tar (michael)
    2. deb
    3. rpm (michael)
  28. Get it tested
    1. Ask dedicated testers for testing their platforms
    2. Consider announcing availability of the new RC in fpc-devel list
  29. Test the GO32v2 release
    1. dos???.zip installation
    2. dos???full.zip installation (over the previously installed dos???.zip to simulate updates)
    3. make sure readme.txt & whatsnew.txt are for the current version
    4. run all executables in /bin/go32v2 (no params)
    5. make cycle with newly installed binaries and sources
    6. run testsuite
    7. open the installed hello.pp in IDE
    8. make a minor change in the demo in IDE & save it
    9. view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
    10. compile the demo file in IDE
    11. run the demo within the IDE (debugger)
  30. Test the OS/2 release
    1. os2???.zip installation
    2. os2???full.zip installation (over the previously installed os2???.zip to simulate updates)
    3. make sure readme.txt & whatsnew.txt are for the current version
    4. run all executables in /bin/os2 (no params)
    5. make cycle with newly installed binaries and sources
    6. run testsuite
    7. open the installed hello.pp in IDE
    8. make a minor change in the demo in IDE & save it
    9. view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
    10. compile the demo file in IDE
    11. run the demo within the IDE (debugger) (not supported)
  31. Test the Win32 release
    1. Run installer
    2. make sure readme.txt & whatsnew.txt are for the current version
    3. run all executables in /bin/win32 (without parameters)
    4. make cycle with newly installed binaries and sources
    5. run testsuite
    6. open the installed hello.pp in IDE
    7. make a minor change in the demo in IDE & save it
    8. view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
    9. compile the demo file in IDE
    10. run the demo within the IDE (debugger)
  32. Test release for i386-freebsd (marcov)
  33. Test release for i386-linux (marcov)
    1. tar
    2. deb (Mazen)
    3. rpm
  34. Test release for powerpc-linux
    1. tar (Thomas)
  35. Test release for powerpc64-linux
    1. tar (Thomas)
  36. Test release for powerpc-macosx
    1. .dmg package (Jonas)
    2. .info file for fink
  37. Test release for i386-macosx
    1. .dmg package (Jonas)
    2. .info file for fink
  38. Test release for powerpc-macos
  39. Test release for powerpc-morphos
  40. Test release for powerpc-amiga
  41. Test release for i386-netware
  42. Test release for i386-netwlibc
  43. Test release for sparc-linux
    1. tar
    2. deb (Mazen)
  44. Test release for arm-linux
    1. tar
  45. Test release for x86_64-linux
    1. tar
    2. deb
    3. rpm
  46. Check PDF documentation (open all files)
  47. Check HTML documentation
  48. Check TXT documentation
  49. Read updated text files as distributed in release zip files
    1. readme.txt
    2. faq.txt
    3. whatsnew.txt
  50. Upload packaged binaries
    • 2.2.1-rc1/source/separate
    • 2.2.1-rc1/source/separate/zip
    • 2.2.1-rc1/source/separate/tar
    • 2.2.1-rc1/source/short
    • 2.2.1-rc1/source/short/separate
    • 2.2.1-rc1/docs
    • 2.2.1-rc1/arm-linux
    • 2.2.1-rc1/i386-freebsd
    • 2.2.1-rc1/i386-go32v2
    • 2.2.1-rc1/i386-go32v2/separate
    • 2.2.1-rc1/i386-linux
    • 2.2.1-rc1/i386-linux/rpm
    • 2.2.1-rc1/i386-linux/deb (Mazen)
    • 2.2.1-rc1/i386-netware
    • 2.2.1-rc1/i386-netwlibc
    • 2.2.1-rc1/i386-os2
    • 2.2.1-rc1/i386-os2/separate
    • 2.2.1-rc1/i386-win32
    • 2.2.1-rc1/arm-wince
    • 2.2.1-rc1/powerpc-linux
    • 2.2.1-rc1/powerpc-macos
    • 2.2.1-rc1/powerpc-morphos
    • 2.2.1-rc1/sparc-linux
    • 2.2.1-rc1/sparc-linux/deb (Mazen)
    • 2.2.1-rc1/x86_64-linux
    • 2.2.1-rc1/x86_64-win64
    • 2.2.1-rc1/powerpc64-linux
    • 2.2.1-rc1/powerpc-macosx
    • 2.2.1-rc1/i386-macosx

FPC-2.2.1-rc2

  1. Section for new RC on release pages in Wiki
    1. Release procedure
    2. Issue log
  2. Look at unmerged changes in fpc and fpcbuild since the last RC and consider/ask for necessity of their inclusion in the release
  3. New directories
.
.

FPC-2.2.2

  1. 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)
  2. New directories
    1. Create new directories on ftp (/pub/fpc/dist/cpu-os-X.Y.Z)
    2. Copy the extra files (asld*.zip, gdb*.zip, make*.zip) from previous RC (unless updated with new versions)
  3. Add new section for the upcoming build in /install/debian/changelog
  4. Create new release branch in SVN
  5. Update version number in release branch to the X.Y.Z
    1. /compiler/version.pas
  6. Create and upload exported fpcbuild
    1. fpcbuild-%{version}.zip
    2. fpcbuild-%{version}.tar.gz
  7. Create and upload the documentation (more info)
    1. doc-pdf.zip
    2. doc-html.zip
    3. doc-htm.zip (not included)
    4. doc-txt.zip
    5. doc-ps.zip
    6. doc-pdf.tar.gz
    7. doc-html.tar.gz
    8. doc-ps.tar.gz
  8. Create and upload source zips
    1. short name version for binary packages
    2. docs source (including link for short name version)
    3. long name version for binary packages
  9. Create and upload zip files for i386-go32v2
    1. basic zip (just binaries)
    2. full zip (including docs and sources)
  10. Create and upload zip files for i386-os2
    1. basic zip (just binaries)
    2. full zip (including docs and sources)
  11. Create and upload installer exe for i386-win32
  12. Create and upload tgz file for i386-freebsd
  13. Create and upload release for i386-linux (more info)
    1. tar
    2. deb
    3. rpm
  14. Create and upload release for powerpc-linux (more info)
    1. tar
  15. Create and upload release for powerpc-macosx
    1. .dmg package
    2. .info files for fink
      1. Build and upload bootstrapcompiler
      2. Update paths, file names and MD5sums, ... in /install/macosx/*.info for the new RC
  16. Create and upload release for i386-macosx
    1. .dmg package
    2. .info files for fink (see powerpc-macosx)
  17. Create and upload release for powerpc-macos
  18. Create and upload release for powerpc-morphos
  19. Create and upload release for powerpc-amiga
  20. Create and upload zip files for i386-netware
  21. Create and upload zip files for i386-netwlibc
  22. Create and upload release for sparc-linux (more info)
    1. tar
  23. Create and upload release for arm-linux (cross-release)
    1. tar - Daniel
  24. Create and upload release for x86_64-linux (more info)
    1. tar
    2. deb
    3. rpm
  25. Test the GO32v2 release
    1. dos???.zip installation
    2. dos???full.zip installation (over the previously installed dos???.zip to simulate updates)
    3. make sure readme.txt & whatsnew.txt are for the current version
    4. run all executables in /bin/go32v2 (no params)
    5. make cycle with newly installed binaries and sources
    6. run testsuite
    7. open the installed hello.pp in IDE
    8. make a minor change in the demo in IDE & save it
    9. view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
    10. compile the demo file in IDE
    11. run the demo within the IDE (debugger) (debugging in IDE currently not available/working)
  26. Test the OS/2 release
    1. os2???.zip installation
    2. os2???full.zip installation (over the previously installed os2???.zip to simulate updates)
    3. make sure readme.txt & whatsnew.txt are for the current version
    4. run all executables in /bin/os2 (no params)
    5. make cycle with newly installed binaries and sources
    6. run testsuite
    7. open the installed hello.pp in IDE
    8. make a minor change in the demo in IDE & save it
    9. view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
    10. compile the demo file in IDE
    11. run the demo within the IDE (debugger) (not supported)
  27. Test the Win32 release
    1. Run installer
    2. make sure readme.txt & whatsnew.txt are for the current version
    3. run all executables in /bin/win32 (without parameters)
    4. make cycle with newly installed binaries and sources
    5. run testsuite
    6. open the installed hello.pp in IDE
    7. make a minor change in the demo in IDE & save it
    8. view documentation in IDE, traverse 2-3 pages (at least one with screenshots)
    9. compile the demo file in IDE
    10. run the demo within the IDE (debugger)
  28. Test release for i386-freebsd
  29. Test release for i386-linux
    1. tar
    2. deb
    3. rpm
  30. Test release for powerpc-linux
    1. tar
  31. Test release for powerpc-macosx
    1. .dmg package
    2. .info file for fink
  32. Test release for i386-macosx
    1. .dmg package
    2. .info file for fink
  33. Test release for powerpc-macos
  34. Test release for powerpc-morphos
  35. Test release for powerpc-amiga
  36. Test release for i386-netware
  37. Test release for i386-netwlibc
  38. Test release for sparc-linux
    1. tar
  39. Test release for arm-linux
    1. tar
  40. Test release for x86_64-linux
    1. tar
    2. deb
    3. rpm
  41. Check PDF documentation (open all files)
  42. Check HTML documentation
  43. Check TXT documentation
  44. Read updated text files as distributed in release zip files
    1. readme.txt
    2. faq.txt
    3. whatsnew.txt

Going public

  1. Make new version numbers (release plus next odd patch number for continuing fixes) available in bug tracker
  2. Make new version numbers (release plus next odd patch number for continuing fixes) available in testsuite db
  3. Make new files on FTP available to wide public
    1. update symlinks (no symlinks any more?)
    2. move the old version to the olddist/<version>
    3. upload files to SourceForge.net and add them to new "releases" for individual platforms
    4. make new "releases" on SourceForge.net accessible for users (change status to "active")
    5. Allow automated notifications on individual SourceForge.net file release pages to be sent
  4. Submit darwin packages to fink
  5. Update WWW pages
    1. /html/news.fp
    2. /html/down/* (links to all individual files & file sizes)
    3. /html/download.fp (version number and list of platforms)
    4. /html/fpc.fp
    5. /html/faq.fp (things like "the latest version is ...")
  6. Create new fixes branch (only after a major release -  ?.?.0)
    1. Update version number in the trunk branch (only after a major release -  ?.?.0)
      1. /compiler/version.pas
      2. All Makefile.fpc files containing "version=..." (plus regenerate the corresponding Makefiles)
  7. Update version number in the fixes branch (increase the patch to next odd number)
    1. /compiler/version.pas
    2. all Makefile.fpc files containing "version=..." (plus regenerate the corresponding Makefiles)
  8. Check the WWW pages
    1. make sure http://www.freepascal.org contains the new version already
    2. read news.html
    3. read fpc.html
    4. read download.html and check links to individual files
  9. Send announcement to our mailing lists
  10. Post announcement on the community site
  11. Post announcement on Sourceforge.net (only "Project Administrators" may do it)
  12. Make sure that all unfixed issues encountered during RC testing and listed on dedicated page in Wiki are documented in bug tracker too
  13. Revise / update /html/future.fp after major versions (?.?.0)
  14. Remove unneeded RC builds from FTP