RFC: Release Plan XML-RPC 2.0

It seems to me to be common sense, that the current tree is almost ready for 2.0. This RFC should help to give a reply to "What's missing?", "Who does it?" and to the details.

What's missing?

I'll list below, what I'd personally see. I suggest that an item should only be allowed to enter the list, if there's a volunteer stepping forward:

Task

Volunteer

Status

Website Upgrade

spoeschl? (As far as I know, you already did most of the work?)

Done

Upgrade to commons-httpclient 3.0

jochen

Checked and patch created, but not yet committed, as 3.0 is still unstable.

Add prerequisite jar files to CVS and distribution (Suggestion)

jochen

Refused

Support for gzip compression

hgomez

Done

Remaining questions: What else?

Open Bugs

I am ignoring bugs, which have been entered before 2004-Jan-1 and bugs with priority normal or less. That leaves

XMLRPC-56

An asynchronous callback object that manages timeouts

XMLRPC-57

Unreleased version XMLRPC_1_2_B2

XMLRPC-58

Incorrect bugreporting address

XMLRPC-59

Missing directories in currently released tarball

All of which either don't apply to 2.0 (XMLRPC-57) or aren't sufficiently serious, IMO.

Questions: Any other bugs we should consider?

Release plan

Questions: Is the above too simple? Do we need separate votes for rc's or the final version? Anyone volunteering to do the releases? If no one else does, I'll do. (Need to create a JaxMe release anyways, so it seems half the work.)

XML-RPC/2.0ReleasePlan (last edited 2009-09-20 22:47:37 by localhost)