Difference between revisions of "Release 2.4.0"
From Free Pascal wiki
Jump to navigationJump to searchLine 17: | Line 17: | ||
# <s> New page in Wiki named "Release_X.Y.Z" 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</s> | # <s> New page in Wiki named "Release_X.Y.Z" 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</s> | ||
# 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]]) | # 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]]) | ||
− | # Move merged changes from [[User Changes Trunk]] to the appropriate [[User Changes | + | # Move merged changes from [[User Changes Trunk]] to the appropriate [[User Changes 2.4.0]] page, possibly adding changes that were merged but not added to the trunk page |
# Ask platform maintainers and [[External_maintainers|external maintainers]] about including their platforms/builds in the new release | # Ask platform maintainers and [[External_maintainers|external maintainers]] about including their platforms/builds in the new release | ||
# Check and update all .msg files | # Check and update all .msg files |
Revision as of 17:48, 28 September 2009
Release Issues
The issues page is Issues 2.4.0
Release preparations
- Agree on deadline for changes and date for release candidate building
- Contact platform maintainers who are not subscribed to the core list and notify them about upcoming release and ask them for their inputs into the release schedule
- Legolas aka Francesco Lombardi - GBA/NDS
- Sekel aka Felipe Monteiro de Carvalho - Symbian
- Olivier Coursiere - Haiku
- Karl-Michael Schindler - Mac OS X - fink
- #FPC-2.4.0rc1 deadline:
- #FPC-2.4.0 deadline:
- Contact platform maintainers who are not subscribed to the core list and notify them about upcoming release and ask them for their inputs into the release schedule
- Check the Detailed 2.4.0 Todo list for the particular release (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_X.Y.Z" 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- 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)
- Move merged changes from User Changes Trunk to the appropriate User Changes 2.4.0 page, possibly adding changes that were merged but not added to the trunk page
- Ask platform maintainers and external maintainers about including their platforms/builds in the new 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 testers page in Wiki (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)
- Update path and file names in /install/macosx/*.info for the new version
- Update path and file names in /install/fpc.ist for the new version
- Finish all source file updates
- convert /html/faq.fp to /install/doc/faq.htm and /install/doc/faq.txt (more info)
RC1
- New directories (more info)
- Create new directories on ftp (/pub/fpc/beta/2.4.0-rcN or /pub/fpc/dist/2.4.0 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 (more info)
- Create new branch in SVN (release_X_Y_Z_rcN or release_X_Y_Z) (more info)
- Update version number in release branch (and, if necessary also in main branch (trunk or fixes)) (more info)
- /compiler/version.pas
- /install/doc/readme.txt
- /install/doc/whatsnew.txt
- /installer/install.dat (header)
- /installer/install.pas (installer version)
- /docs/fpc.sty (macro fpcversion)
- All Makefile.fpc files containing version=... (plus regenerate all corresponding Makefiles) (more info)
- All version-numbers in fpmake.pp files (more info)
- Create and upload exported fpcbuild (more info)
- fpcbuild-%{version}.zip
- fpcbuild-%{version}.tar.gz
- fpc-%{version}-source.zip
- fpc-%{version}-source.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 (more info)
- short name version for binary packages
- docs source (including link for short name version)
- long name version for binary packages
- Create and upload binary releases (place the bame of the person who aggreed to build a release behind the name of the target below)
- i386-go32v2/basic zip (just binaries)
- i386-go32v2/full zip (including docs and sources)
- i386-os2/basic zip (just binaries)
- i386-os2/full zip (including docs and sources)
- i386-win32/exe
- x86_64-win64/exe
- arm-wince/exe (cross-release)
- arm-symbian (cross-release)
- i386-symbian (cross-release)
- arm-gba (cross-release)
- arm-nds (cross-release)
- i386-freebsd/tgz
- i386-linux/tar (more info)
- i386-linux/deb (more info)
- i386-linux/rpm (more info)
- x86_64-linux/tar (more info)
- x86_64-linux/deb (more info)
- x86_64-linux/rpm (more info)
- powerpc-linux/tar (more info)
- powerpc64-linux/tar (more info)
- powerpc-macosx/dmg
- i386-macosx/dmg
- i386-macosx/.info for fink
- powerpc-macos
- sparc-linux/tar (more info)
- sparc-linux/deb (more info)
- arm-linux/tar (cross-release)
- powerpc-morphos
- powerpc-amiga
- i386-netware
- i386-netwlibc
- i386-haiku
- sparc-sunos/tar
- Get it tested
- Ask dedicated testers for testing their platforms
- Consider announcing availability of the new RC in fpc-devel list
- Keep track of testing in the wiki
-- End of template for every version
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
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)
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 - 2.4.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 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 (2.4.0)
- Remove unneeded RC builds from FTP