1) state loud and clear that the direction is Gumpy and retire traditional gump, this will help creating itches to scratch
+1
2) refactor our CVS module:
gump-traditional gump gump-data
hmm. Split between code and data seems sensible, but I don't really get why we want gump-1.0 and gump-2.0 in seperate repos?
3) stop calling it gumpy but rather start doing version numbering, so that would be Gump 2.0, when Gump 1.0 was traditional
+1
4) add a cron job so that [EMAIL PROTECTED] becomes the official gump run.
+1
-- cheers,
- Leo Simons
----------------------------------------------------------------------- Weblog -- http://leosimons.com/ IoC Component Glue -- http://jicarilla.org/ Articles & Opinions -- http://articles.leosimons.com/ ----------------------------------------------------------------------- "We started off trying to set up a small anarchist community, but people wouldn't obey the rules." -- Alan Bennett
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
