Hi, New version of the release plan. Step 1 is already done.
NEdit 5.6 "Mark Twain"
Release Plan v1.2
1. Determine release-critical bugs
Meaning we should all huddle and create a list of things that have to
be fixed before RC1. This would include stuff from the SF tracker but
also anything else we could come up with.
The situation in the bug tracker is really beyond silly. Eddy wrote in
his mail kicking off the 5.4 release: "The list of open bugs at SF is
getting far too long." We had around 70 entries then, we now have more
than a hundred.
When we have a list we can agree on, we enter the bugs into the SF
tracker (most should already be in) with a priority of 9.
Bugs introduced after the last release should get special consideration.
2. Fix bugs
There are currently two release-critical bugs left:
#1600102 Add example .nedit to release tarball
This is a pseudo-bug, as nothing is really wrong here. The work is
largely done, the result should be checked by others though.
#1027807 loss of files on full disk
A solution is discussed. A patch limiting the damage is already there,
a better solution does not look so hard.
3. Wait until we think the bug fixes are settled. In this time:
a) Update ReleaseNotes
Anything missing? (Also general copyedit)
b) Prepare release announcements for RCs and release
c) Documentation
Check URLs, file names (.nedit -> nedit.rc), tabs/tab stops and
similar details.
c) Set up build options for various platforms
d) Update language modes
e) Identify people who would do pre-builds
OS CPU Other OS want OS have Tested on Contact
AIX rs6000 4.3.3 4.3.3 4.3.3, 5.1 - 5.3 Andrew Hood
<[EMAIL PROTECTED]>
(old list from 2003-06-16)
OS CPU Other OS want OS have Tested on Contact
AIX rs6000 4.2 4.3.3 AIX 4.2 - 5.0 [EMAIL
PROTECTED]
HPUX HPPA 10 10.10 HPUX 10-11 [EMAIL
PROTECTED]
IRIX MIPS 5.2 5.3 IRIX 6.2, 6.5.5 [EMAIL
PROTECTED]
Linux Alpha RH5.2 RH 5.2 - 7.0 ST
Linux x86 libc5 RH5.2 RH 5.2 - 7.1 ST
Solaris Sparc 2.5.1 5.5.1 5.5.1, 5.6, 5.7, 5.8 ST
Solaris x86 2.5.1 5.6 5.6 ST
Tru64 alpha 3.2 4.0B OSF 4.0* ST
The SF compile farm offers quite a lot of platforms, but NEdit
won't run on them (no X11). I asked them to install Xvfb, we could
then use some macros, Imagemagick's import and X11::GUITest to test
basic functionality. Also, SF discourages use of the compile farm
to create packages. Obviously not the best imagineable solution.
Maybe we can find a way in which pre-builds can be done simpler
than before. This would free the way for faster release cycles.
f) Identify new known-good/bad versions of Lesstif and put them in the
test program and the release notes.
g) Update website:
- build.php does only mention ./util and ./source.
4. Update Changelog
5. Branch BETA-5-6
6. Create release candidate
1. Tag BETA-5-6-RCn on branch BETA-5-6
2. Create source tarball
3. Create pre-builds
4. Post release announcement
5. Wait for bugs coming in.
6. Repeat until regression bugs are done
7. Tag REL-5-6
8. Create pre-builds
9. Post release announcement
10. Merge release branch back to MAIN
Thorsten
--
A witty saying proves nothing.
- Voltair
pgp4INGFfojRp.pgp
Description: PGP signature
-- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
