-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rodent of Unusual Size wrote:
> if we do a release now, bear in mind that we'll probably need to > do another one. at this point, unless i'm mistaken we'd just be > covering mostly beaten ground, since no changes have been made > to derby. it would be a good exercise for everyone to get familiar > with the release process, but i'd think we'd need to do another > after we've actually made some changes and tested them. [maybe a case of not quoting enough in your reply Ken :-)] My initial e-mail said >> Are there any thoughts on if the current Derby code is ready, >> and if the community should start thinking about an initial release? >> Obviously some of the patches submitted so far to fix bugs would >> need to be committed first, once commit access is available! Thus I wasn't thinking about a release *now*, but after at least some bug fixes. But I was really looking for what folks think should be done for a release. Dan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBQfS9Iv0S4qsbfuQRAjc2AKCDjbpNPQxx9XnUXomn7DRbIA4QqwCglweL KLhDrtIKd7XhahVEQEbTmeo= =OcCv -----END PGP SIGNATURE-----
