Now that we have gump running on an apache machine
Yeah
+1
http://moof.apache.org:8080/gump/
that will soon proxypassed from
http://gump.apache.org/results/
I propose a few actions:
1) state loud and clear that the direction is Gumpy and retire traditional gump, this will help creating itches to scratch
2) refactor our CVS module:
gump-traditional gump gump-data
gump-1.0 gump-2.0 meta-data
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
thoughts?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
