Hi James,
1. Make a source tarball that has the proper autoconf files already
created.
2. Make install packages for common distributions (probably RPM - I can do
Slackware because that's what I use - is there something specific for
BSD?)
3. Make windows executable.
Carey always told me to use the latest version of config.guess and
config.sub. Here's a conversation we had:
http://archive.midrange.com/linux5250/200304/msg00025.html
So you may need to start by updating those...? I don't know if this
requires committing changes to CVS or not, it's been too long.
In the CVS repo, make sure configure.ac has the version set to 0.17.4,
and also add an entry into ChangeLog saying "released version 0.17.4"
and commit these changes.
Hopefully at this point, the CVS repo has everything it needs, and won't
need to change again before the release. That being the case, I would
set a v0-17-4 tag in the repo. That way, years from know we'll know
exactly which code was used for the 0.17.4 release.
Next, I'd delete my tn5250 sandbox and check out a fresh one from CVS
using the v0-17-4 tag -- this guarantees that you're using the code you
think you are :)
autogen.sh, configure, make, make dist and make distcheck to verify that
it's all healthy. (Though, I just tried this, and it's not healthy.
SLang support appears to still be broken from when you reorganized the
source tree.)
to summarize, this is what I think the build process (for a release)
should be:
1. Get the latest config.sub & config.guess
2. Verify the versions & add a "version XXX" released message to ChangeLog
3. Commit Updates from Step 2.
4. Set the v0-17-4 tag.
5. Update the configure.ac file with 0.17.5 for the version so it's
ready for future development, and commit that.
6. Check out a fresh CVS from tag v0-17-4
7. cd tn5250 && ./autogen.sh && ./configure
8. make dist
9. make distcheck
10. Send the output from make dist (tn5250-0.17.4.tar.gz) to me
11. I'll verify that the release works on FreeBSD (I'm assuming you
verified it on Linux)
12. I'll build Windows binaries.
13. I'll upload your tarball, plus the Windows binaries to Sourceforge.
I don't know how to create/test RPMs and no longer have easy access to a
Linux box, so I can't help with that. If nobody volunteers, I agree
that we shouldn't worry about RPMs. If someone does volunteer, I'll
send that person the tarball after verifying that it works on FreeBSD,
and I'll wait for the RPMs before uploading to SF.
Don't worry about FreeBSD packages, we don't normally keep those on the
TN5250 site, rather FreeBSD takes care of them.
I think that's everything?
midrange.com
