Difference between revisions of "1.9.6 Todo"
From Lazarus wiki
Jump to navigationJump to search(3 intermediate revisions by the same user not shown) | |||
Line 14: | Line 14: | ||
* readme.txt updates for *nix (there was some complaint either in bug repository or lists) | * readme.txt updates for *nix (there was some complaint either in bug repository or lists) | ||
* <strike>(Optional) test AMD64 Linux under FC3</strike> | * <strike>(Optional) test AMD64 Linux under FC3</strike> | ||
− | * Fix Lazarus on X11 on Mac OS X | + | * <strike>Fix Lazarus on X11 on Mac OS X</strike> |
* <strike>searching for fpc.cfg should search $prefix/fpc.cfg</strike> | * <strike>searching for fpc.cfg should search $prefix/fpc.cfg</strike> | ||
* <strike>MorphOS: syscalls need to be fixed</strike> | * <strike>MorphOS: syscalls need to be fixed</strike> | ||
Line 22: | Line 22: | ||
== Release procedure ([[Release Template]]) == | == Release procedure ([[Release Template]]) == | ||
− | # Check and update all .msg files | + | # <strike> Check and update all .msg files </strike> Skipped for this releaes, too much work for now. |
## errore.msg | ## errore.msg | ||
## errord.msg | ## errord.msg | ||
Line 39: | Line 39: | ||
## /compiler/version.pas | ## /compiler/version.pas | ||
## /install/doc/readme.txt | ## /install/doc/readme.txt | ||
− | ## /install/fpinst/install.dat (header + cfg template) | + | ## <strike>/install/fpinst/install.dat (header + cfg template)</strike> |
− | ## /install/fpinst/install.pas (installer version) | + | ## /install/fpinst/install.pas (installer version) <i>Not necessary?</i> |
## /install/fpc-docs.spec | ## /install/fpc-docs.spec | ||
## /install/fpc.spec | ## /install/fpc.spec | ||
Line 47: | Line 47: | ||
## convert /html/faq.fp to /install/doc/faq.htm and /install/doc/faq.txt | ## convert /html/faq.fp to /install/doc/faq.htm and /install/doc/faq.txt | ||
## /docs/fpc.sty (macro fpcversion) | ## /docs/fpc.sty (macro fpcversion) | ||
− | # Update whatsnew.txt (/install/doc/whatsnew.txt) | + | ## All Makefile.fpc files containing version=... (plus regenerate all corresponding Makefiles) |
− | # Finishing all source file updates | + | # <strike>Update whatsnew.txt (/install/doc/whatsnew.txt)</strike> |
+ | # Finishing all source file updates (= updates frozen until release) | ||
# Tag CVS with RELEASE_?_?_? | # Tag CVS with RELEASE_?_?_? | ||
# Create and upload zip files for GO32v2 | # Create and upload zip files for GO32v2 |
Revision as of 18:52, 29 December 2004
General Todo
improve external behaviourimprove -Or resultsprevent inlining crashes when referencing static procedures/vars (tw3340)- (optional) look through IDE bugs
- Integrate system unit and objpas unit in fpdoc
- Update man page for new options
- Update docs for new default paths
- Update fpcmake docs for new default paths
- Test i386 Linux under FC3
Fix bugs in installer (probably related to FVision)install.dat updates for os/2- readme.txt updates for *nix (there was some complaint either in bug repository or lists)
(Optional) test AMD64 Linux under FC3Fix Lazarus on X11 on Mac OS Xsearching for fpc.cfg should search $prefix/fpc.cfgMorphOS: syscalls need to be fixed- MorphOS: (optional) add pure SysV syscalls
- MorphOS: (optional) add support for array of const in syscalls
Release procedure (Release Template)
Check and update all .msg filesSkipped for this releaes, too much work for now.- 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, util*.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) Not necessary?
- /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)
- All Makefile.fpc files containing version=... (plus regenerate all corresponding Makefiles)
Update whatsnew.txt (/install/doc/whatsnew.txt)- Finishing all source file updates (= updates frozen until release)
- 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
- 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 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)