Adam R. B. Jack wrote:
My problem is that suggestion of a -1 ... 'cos although we won't actually
stop folks running traditional Gumps, we aren't wanting to maintain two
metadata trees, we aren't wanting to maintain Traditional to work on current
metadata. Traditional will (with Jakarta Commons so Mavenized) quickly
become unworkable.
Sebastian wrote:
But -1 if the proposal is to stop non-Python Gumps at present.
How about a compromise? Here is my proposal:
Fork the metadata tree (perhaps putting the new one in SVN) and make it very clear that the gumpmeisters have no intention of maintaining the traditional metadata themselves (but anyone with commit priviledges may modify the traditional metadata if they so wish - the latter is no different to the way things are now).
Whenever a project wants to switch from ant to maven builds, the gumpmeisters will strongly recommend that the equivalent traditional metadata is deleted from CVS, but the final decision will rest with the actual project team. This means that over time the traditional gump's view of the universe will shrink, but people can still make their private traditional gumps do whatever they want.
We state that Java gump is now in "sustaining" (or equivalent wording) - no new features will be added but we may choose to make critical bug fixes. Python gump is the version that people should be using. We leave retiring the traditional metadata until the Python performance problems have been addressed (congrats on the progress with this, by the way).
-- Michael
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
