Berin Loritsch wrote:
I thought I did volunteer. If it wasn't clear, I do.
whoohooh! +1 for Berin as release manager :D
Don't we want to build ECM and it's dependencies against the new framework release?You know, it may be better to do it in this fashion: LogKit Excalibur (ECM dependencies) ECM Framework Excalibur (Fortress dependencies) Fortress Excalibur (all remaining) Cornerstone Phoenix Merlin
IOW, the below schedule (dependency list based on current gump output, things between () already released higher up the schedule)
1) Logkit 1.1.2 (stable release)
2) Framework 4.1.4 (stable release)
3) ECM Dependencies (stable releases)
- excalibur-container
- excalibur-pool
- excalibur-logger
- excalibur-event
- excalibur-collections
- excalibur-instrument
- excalibur-instrument-manager
- excalibur-altrmi*
4) ECM 1.1 (stable release)
Fortress Dependencies (stable release)
(- excalibur-altrmi*)
(- excalibur-instrument)
(- excalibur-instrument-manager)
- concurrent (doug lea's concurrency package)
(- excalibur-container)
(- excalibur-event)
(- excalibur-logger)
- excalibur-sourceresolve
- excalibur-thread
5) Fortress 1.0 (alpha, beta, stable releases)
Phoenix dependencies (stable releases)
- excalibur-configuration
- excalibur-converter
- excalibur-io
(- excalibur-info <-- gump definition error I guess, this was
moved back into phoenix)
- excalibur-cli
- excalibur-extension
- excalibur-threadcontext
(- excalibur-thread)
(- excalibur-pool)
(- excalibur-loader)
(- excalibur-logger)
(- excalibur-i18n)
- excalibur-baxter
- excalibur-policy
- excalibur-monitor
- excalibur-util
6) Phoenix 4.1 (beta & stable releases)
7) Cornerstone dependencies (stable releases)
(- excalibur-io)
(- excalibur-datasource)
(- excalibur-i18n)
(- excalibur-thread)
(- excalibur-threadcontext)
(- jakarta-avalon-phoenix <-- this is why phoenix needs to go
first)
(- excalibur-event)
(- excalibur-altrmi*)
(- excalibur-converter)
(- excalibur-util)
(- excalibur-loader)
(- excalibur-monitor)
(- excalibur-policy)
(- excalibur-configuration)
(- excalibur-extension)
(- excalibur-pool)
(- excalibur-baxter)
(- excalibur-logger)
(- excalibur-info <-- gump definition error I guess, this was
moved back into phoenix)
(- excalibur-cli)
8) Any remaining excalibur packages (stable and perhaps a few
alpha or beta releases)
Cornerstone (dunno what status)
Phoenix demo apps (alpha release)
9) perhaps maintainance releases and catching of any problems
merlin (alpha, beta, stable releases)
* if we don't want AltRMI released, we need to make it an optional depencency.
I've tried to sort-of list things that happen concurrently together. Of course, we can always do alpha and beta releases earlier up the list. For example, we might want to do a merlin alpha somewhere around bullet 5 already.
Berin, I'd say you are most suited to do (1-5), while it'd be cool if one of the phoenix experts (paul?) can do (6). I think it'd be good to have Steve handle cornerstone (7) and merlin (9). Good idea? Me, I would like to keep focussing on docs, infrastructure 'n stuff and helping out with QA :D
cheers,
- Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
