Difference between revisions of "Release Template"
From Free Pascal wiki
Jump to navigationJump to searchm (util*.zip built within release, not copied from old) |
|||
Line 9: | Line 9: | ||
# New directories | # New directories | ||
## Create new directories on FTP and set permission to 700 (using a script ...?) | ## Create new directories on FTP and set permission to 700 (using a script ...?) | ||
− | ## Copy the extra files (asld*.zip, gdb*.zip, make | + | ## Copy the extra files (asld*.zip, gdb*.zip, make*.zip) from the old release |
# Check tools | # 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 | ## 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 |
Revision as of 16:09, 27 December 2004
- Check and update all .msg files
- errore.msg
- errord.msg
- errorf.msg
- errorn.msg
- errorr.msg
- errorrw.msg
- errores.msg
- New directories
- Create new directories on FTP and set permission to 700 (using a script ...?)
- Copy the extra files (asld*.zip, gdb*.zip, make*.zip) from the old release
- 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 version number in the appropriate CVS branch
- /compiler/version.pas
- /install/doc/readme.txt
- /install/fpinst/install.dat (header + cfg template)
- /install/fpinst/install.pas (installer version)
- /install/fpc-docs.spec
- /install/fpc.spec
- /install/install.sh
- /html/faq.fp (things like "the latest version is ...")
- convert /html/faq.fp to /install/doc/faq.htm and /install/doc/faq.txt
- /docs/fpc.sty (macro fpcversion)
- Update whatsnew.txt (/install/doc/whatsnew.txt)
- Finishing all source file updates
- Tag CVS with RELEASE_?_?_?
- Create and upload zip files for GO32v2
- Create and upload zip files for OS/2
- Create and upload zip files for Win32
- Create and upload tar files for FreeBSD
- Create and upload tar files for Linux
- i386
- powerpc
- sparc
- x86-64
- arm
- Create and upload Linux RPMs
- i386
- sparc
- x86-64
- powerpc
- arm
- Create and upload Linux DEBs (ask DEB maintainer)
- i386
- sparc
- x86-64
- powerpc
- arm
- Create and upload the documentation
- docs-pdf.zip
- doc-html.zip
- doc-htm.zip
- docs-txt.zip
- Create and upload source zips
- Create and upload source tars
- Run makereleasezips
- 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)
- Test the Win32 release
- w32???.zip installation
- w32???full.zip installation
- dosw32???full.zip installation (over the previously installed w32???full.zip to simulate updates)
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/win32 and /bin/go32v2 (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 the FreeBSD release
- FreeBSD tar installation
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/freebsd (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 Linux DEBs
- Linux DEBs installation
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/linux (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 Linux RPMs
- Linux RPMs installation
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/linux (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 Linux tar release
- Linux tar installation
- make sure readme.txt & whatsnew.txt are for the current version
- run all executables in /bin/linux (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)
- 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
- Make new files on FTP available to wide public
- open new directories for public access
- update symlinks
- move the old version to the olddist/<version>
- Update WWW pages
- /html/news.fp
- /html/download.fp (links to all individual files & file sizes)
- /html/fpc.fp
- 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 _all_ links to individual files
- Send announcement to our mailing lists
- Post announcement on the community site
- Revise / update /html/future.fp after major versions (?.?.0)