> Timeline:
> (All days ending at 23:59:59 GMT in case of dispute.)
>
> * Review Period
> Thursday, August 30 2001 - Thursday, 13 September 2001
>
> During the Review Period specific design, functional and
> contract changes to HTTP Client will be considered on the
> Jakarta-Commons mailing list, using the following
> process:
>
> 1) Any developer or committer that would like to see
> a specific change (or group of changes) enacted or
> rolled back will suggest it on the Jakarta-Commons
> mailing list ([EMAIL PROTECTED]).
>
> 2) Any interested committer that opposes a given change
> (or group of changes) is obligated to indicate this
> disapproval on the list during the Review Period.
>
> 3) We will seek, but not strictly require consensus on
> each decision point. If consensus cannot be reached,
> any committer may call for a vote to resolve the
> issue via a lazy majority vote.
>
> Since substantial progress has been made on a number of
> the objectives within the "rlwrefactoring" branch of HTTP
> Client within the CVS tree, it is suggested that we use
> that revision as a starting point. Of course, no changes
> within that branch are set in stone. (Indeed, even the
> author of those changes has several things he'd still
> like to reconsider.) One summary of the major changes
> in this branch versus the current main branch of HTTP
> Client can be found at:
>
>
>
http://www.mail-archive.com/[email protected]/msg03954.html
>
> The Review Period may be closed before 13 September 2001,
> given one "workday"'s notice and lazy majority approval.
>
> The Review Period may be extended by one week (at a time)
> given lazy majority approval, in case issues still need
> to be resolved.
>
> * Implementation Period
> Friday, 14 September 2001 - Monday, 24 September 2001
> (assuming the Review Period is not extended)
>
> During this period, any remaining implementation, testing
> and documentation will be completed. No new features
> or "public" interface changes will be considered
> in-scope at this time (short of a lazy-majority
> approved revised release plan or any "showstopper"
> defects).
>
> At the end of the Implementation Period, a formal
> release vote will be called, subject to lazy
> approval.
>
> A formal release vote may be called before 24 September,
> but after the end of the Review Period, if appropriate.
I think the development period is too short to allow a successful
refactoring of the component. I would suggest extending it by 2 to 4 weeks.
So -0 as is, and +1 with the extended implementation period.
Remy
