[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Preparing for 0.06 release
From: |
Mark Wielaard |
Subject: |
Preparing for 0.06 release |
Date: |
10 Aug 2003 16:40:23 +0200 |
Hi all,
A little reminder. We want to release a new GNU Classpath snapshot
release (0.06) next Friday (August 15).
Things to do/decide before the release:
- What should really go in before the release?
- There are still some open bugs:
http://savannah.gnu.org/bugs/?group=classpath
Not all are analyzed yet, but although it would be nice to fix/close
some of these there don't seem to be any showstoppers.
- There is still one open patch for SecurityManager/VMSecurityManager
http://savannah.gnu.org/patch/?func=detailpatch&patch_id=1031&group_id=85
Don't know how urgent this is. I would like to see a real design how
to handle this and related methods in a VM independent way, but that
is probably not 0.06 material. (JRVM hackers, how important is it
that this goes in? We can always add a hack for 0.06 if that really
helps you out.)
- Is there any progress on the Thread/VMThread split?
Would be nice to get that in, but it will require work to make it
work with the different VMs so it better go in quickly
(today/tomorrow).
- Is something else important missing? Please email me/the list with
suggestions.
- Creating release tar balls.
I am playing with this now. It seems that this is not to difficult
(Just type: make dist). Have to check to things:
- How to get gjdoc installed and generate correct api documentation.
- Why my make install does not create any plain .so files
(The .0, .0.0.0 and .la do get installed, but I have to symlink the
.so to the .0.0.0 files by hand...)
- Update the NEWS file.
- It contains all VM interface changes which is good.
- It should contain all important additions/bug fixes made for this
release. This can be done by going through the bug/patch database
and the ChangeLog file. (Any volunteers?)
- Bumping the version number and tag the CVS treee (DON'T FORGET!)
- Will do this just before the final release.
- Upload the release to alpha.gnu.org
- Some yoyo thought it would be funny to crack the main GNU file
server. So they had to disable all accounts, reinstall the whole
machine and clean everything up :{ Hopefully this will be done
before Friday, otherwise we have to host the tar ball somewhere else
for the moment.
- Create release notes and post them to relevant forums.
- Should be easy by taking the news items regarding older releases
<http://savannah.gnu.org/news/?group=classpath> and combine them
with the NEWS items.
Cheers,
Mark
- Preparing for 0.06 release,
Mark Wielaard <=
- Re: Preparing for 0.06 release, David P Grove, 2003/08/11
- Re: Preparing for 0.06 release, Ito Kazumitsu, 2003/08/14
- Re: Preparing for 0.06 release, Mark Wielaard, 2003/08/14
- Re: Preparing for 0.06 release, Brian Jones, 2003/08/14
- Re: Preparing for 0.06 release, Brian Jones, 2003/08/14
- Re: Preparing for 0.06 release, Mark Wielaard, 2003/08/15
- Re: Preparing for 0.06 release, Mark Wielaard, 2003/08/15
- Re: Preparing for 0.06 release, Mark Wielaard, 2003/08/15
- Re: Preparing for 0.06 release, Arnaud Vandyck, 2003/08/15