* TODO.html, README.html: Remove these old files.
* AUTHORS, COPYING, ForRelease, NEWS, ToDo: Update for release. * eo.cfg (PROJECT_NUMBER): Bump version to 1.0
This commit is contained in:
parent
51d6ddc239
commit
0afa0b9fa4
11 changed files with 51 additions and 165 deletions
|
|
@ -1,14 +1,16 @@
|
|||
In oder to create a new release from the current cvs sources perform
|
||||
the following steps:
|
||||
In order to create a new release from the current cvs sources perform the
|
||||
following steps:
|
||||
|
||||
- Set version number in configure.in and doc/eo.cfg.
|
||||
- Set version number in configure.in and doc/eo.cfg
|
||||
- Check/update NEWS file, set release date and version in NEWS.
|
||||
- Run `make check && make dist`.
|
||||
- Test distribution (unpack, configure, make check).
|
||||
- Put distributions at SourceForge.
|
||||
- Post news on SourceForge project-page.
|
||||
- Send announcement to mailing lists.
|
||||
- Bump version number to next x.y.z-cvs in configure.in and doc/eo.cfg.
|
||||
- Run `make check && make dist`
|
||||
- Test distribution (unpack, configure, make check)
|
||||
- Tag released code in cvs, in order to allow a branch to be created at that
|
||||
version if the necessity will arise later
|
||||
- Put distribution files at SourceForge
|
||||
- Post news on SourceForge project-page
|
||||
- Send announcement to mailing lists
|
||||
- Bump version number to next x.y.z-cvs in configure.in and doc/eo.cfg
|
||||
|
||||
# Local Variables:
|
||||
# coding: iso-8859-1
|
||||
|
|
|
|||
Reference in a new issue