-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 One of the criteria for Derby exiting incubation is to have 'One or more Releases of the package during the incubation phase'. http://incubator.apache.org/derby/derby_proposal.html#Section+6+%3A+Incubation+Exit+Criteria
An example of a release process at Apache is here http://httpd.apache.org/dev/release.html for the HTTP server. As a project in incubation, Derby has some restrictions on release discussed here: http://incubator.apache.org/incubation/Incubation_Policy.html#Releases%0A 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! I believe that a release of Derby would attract more users, having downloadable pre-built jar files would help those who don't want to get into building Derby from scratch. A release would also may need some decisions to be made like will there be future bug fix releases of the release and will databases built from the release be upgradable to future versions of Derby? Dan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBPi6LIv0S4qsbfuQRAu1VAJ9Rzc4Ku6J/+bce+Nl2gJQRy/Sy3gCghqS7 ICCDD4MlL+6Iwbw7VCrA/S4= =Jb2H -----END PGP SIGNATURE-----
