Leo Simons wrote:
Berin Loritsch wrote:
We should do the minimal ECM set, and then the full Cocoon
required set. Lastly, we should do the Fortress set.
uhm...me, I would like to do fortress before cocoon. Getting that out is
a higher priority for me (and its less subprojects, too) than getting
cocoon upgraded to use the latest and greatest avalon jars.
Specifically, I don't really feel like having to do new releases of all
the stuff that really shouldn't be released just yet, or anymore. Too
much headache. Just 2pc; your call as RM :D
Sounds good. We can rearrange the order of those two. I thought
about that as well...
That said, I think it is vital we get a few gump runs where cocoon cvs
builds against avalon cvs before we release _any_ excalibur libraries;
this to ensure we're remaining backwards-compatible. It's proving to be
difficult to get things running (http://nagoya.apache.org/~rubys/gump/
shows the latest puzzling failure :/).
Ok.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
