What does Phase I, II or III mean? Is it just an ordering,
or does it imply that e.g. projects in Phase III are not that
stable or something is missing there etc.?

I think we can move store and xmlutil from Phase III to Phase II
as they both should be stable and are working well.

Carsten

> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 06, 2003 9:17 PM
> To: [EMAIL PROTECTED]
> Subject: Evening out the Release Schedule
> 
> 
> We currently outlined three phases of Excalibur releases planned.
> The first to get a current version of ECM ready.  The second to
> get Fortress 1.0 ready.  And the last to release the current
> snapshot of all previously released Excalibur code.  That's alot
> of packages.
> 
> Currently the table for the release schedule looks like this:
> 
> Phase I            |  Phase II        |  Phase III
> -------------------+------------------+-------------------
> component          | container        | cli
> instrument         | event            | collections
> instrument-manager | fortress         | datasource
> logger             | sourceresolve    | instrument-client
> pool               | xfc              | io
> testcase           |                  | monitor
> i18n               |                  | naming
>                     |                  | store
>                     |                  | thread
>                     |                  | threadcontext
>                     |                  | xmlutil
>                     |                  | concurrent
> 
> Which still leaves the following Excalibur projects that have never
> been released (to my knowledge)--if there is a link to a public
> download of any of these, let me know:
> 
> cache
> configuration
> converter
> csframework
> extension
> jprocess
> loader
> policy
> 
> As you can see things are rather heavily slanted towards Phase III
> which means that it is going to take a long time.  Things which were
> previously released, but are no longer recommended/supported should
> be merged into a new "compat" library which will be available so that
> our users can migrate at their leasure.  The current projects taht
> should go in the "compat" library are:
> 
> cli (--> Commons CLI)
> collections (--> Commons Collections)
> concurrent (--> Doug Lea)
> io (--> Commons IO?)
> naming (--> ?)
> 
> Nothing in the compat library will be deprecated unless there is a
> clear alternative such as the case with collections and concurrent.
> 
> As to the remaining projects in the "scratchpad" list that are not
> in the proper repository, we have to decide if #1 we want to continue
> incubation, and #2 move those that we want to keep to scratchpad.
> For some of them, the move was done and all that remains is deleting
> the archive from Excalibur.
> 
> Lastly, I was wondering if it would be OK with some folks to upgrade
> some of the projects from Phase III to Phase II.  That way we can
> maintain a fairly constant work load.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to