Niclas wrote this (on community, and found archive). Bringing it here for continuation:
[...] > Now, what do we do with the Phoenix codebase in ASF?? > > GUMP makes this apparent. When changes are made in CVS in projects that > Phoenix depends on, we will receive Nags. These are of three types; > 1. Temporary and will disappear by themself. > 2. Incompatible change in other project, by mistake or un-awareness. > 3. Permanent Incompatible change. 1.0 -> 2.0 > > By upgrading Phoenix to these changes, seems fairly meaningless. > > Killing the Gump descriptor seems like the most logical thing to do, but that > would affect projects that depends on it (or other similar cases), James in > this case, I think. Assuming that Phoenix goes into archive, what do we do for James (and others)? There are a few: http://lsd.student.utwente.nl/gump/avalon-phoenix/avalon-phoenix/details.html#Project+Dependees Things below Phoenix are still developing, and can (have?) break Phoenix. As such, we can't even package Phoenix & expect success for James and such. Any thoughts on how we deal with this? regards Adam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
