Thanks Craig. We'll try and create a first test release soon.
I don't see gnupg in sfw on solaris - do you know where I can get it ?
sunfreeware.com lists dependancies that I know I'm going to run into
trouble with (openldap, readline etc.)
Shanti
On 02/23/09 22:05, Craig L Russell wrote:
Hi,
This list looks like a good one. In parallel, you might add a task to
prepare instructions for the release itself. In case you haven't seen it
yet, please read http://incubator.apache.org/guides/releasemanagement.html.
The process looks complicated but it's really not. Whoever prepares the
release needs to get a signing key and add it to the KEYS file. All
release artifacts (.zip, .tar, .tar.gz, etc) need to be signed with .asc
and checksummed with .md5. A typical release has a dozen or so files
including checksums and detached signatures.
The release needs to be verified for functionality (does it unzip and
build) but for licensing correctness (all the NOTICE files are present,
all files are properly headed with the Apache license header). There is
a tool called RAT that needs to be run on the release artifacts.
It would be good to start preparing the release even while polishing off
the gating bugs.
Craig
On Feb 23, 2009, at 5:39 PM, Shanti Subramanyam wrote:
Here is the task list I came up with for things that need to be done for
the release. Please do correct, add etc. and I'll collect everyone's
input and post the final version. Note that I've picked only certain
pending issues that I thought were critical. Please review the full
list to see if any others need to be fixed. In particular, I have not
added the merge of the driver, loader(s) code between the
implementations. I think we will be resource constrained to get this
done but Akara and Will can chime in.
Task List
=========
File JIRA's for these issues and fix:
. Add caching as a configurable option to the rails application.
. Update the rails db and file loaders from the php version.
. Test rails app with new db scale (100x Users) and check-in fix for
OLIO-51 (Will has filed OLIO-54 which involves schema changes)
. Issues to fix:
OLIO-53 Database load fails at high user counts
https://issues.apache.org/jira/browse/OLIO-53
OLIO-52 Web application consumes increasingly more time as run
progresses
https://issues.apache.org/jira/browse/OLIO-52
OLIO-51 Increase scale/size of database
https://issues.apache.org/jira/browse/OLIO-51
OLIO-33 Change 'web20' names everywhere to 'olio'
https://issues.apache.org/jira/browse/OLIO-33
OLIO-29 Driver does not check for accuracy in throughput to
determine pass/fail
https://issues.apache.org/jira/browse/OLIO-29
OLIO-13 License/copyright info in source files is incorrect
https://issues.apache.org/jira/browse/OLIO-13
OLIO-3 Caching needs to be implemented in PHP application
https://issues.apache.org/jira/browse/OLIO-3
. Update setup instructions to work on released tar bundle
. Update spec doc (it's currently very minimal)
. Add top-level ant script for each implementation to build release
. Add release notes
. Edit web page to add download links.
. Create and test release.
Shanti
Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:[email protected]
P.S. A good JDO? O, Gasp!
