On Wed, Feb 18, 2004 at 10:48:43AM -0800, Matt Massie wrote: > guys- > > i would like some feedback here. i have the CVS setup now to email me > all the checkins and diffs. would you like me to have it mail the > developers list? > > another option is to create a new mailing list, say "ganglia-checkins" > which you can subscribe to.
Either one of these would be great. I'd been meaning to ask for this for a while. I'd suggest naming the list ganglia-cvs since that's a pretty common convention. It would be really nice to know when changes are made rather then hoping someone posts a summary. > having the checkins mailed to the developers list shouldn't increase the > number of messages much at all. one important note though is that the > CVS log messages are included in the messages (along with the diffs). > it's important that if we setup a public list to monitor checkins that > we don't put in any crazy log messages since they are all archived. Since they are all visiable in the repo, I would hope people weren't doing too much of this now... > on a completely different note. ganglia 3. i'm going to be pounding on > the 2.5.x code to get it in shape for new features: metric modules, rss > alerts, and a hierarchical namespace. when it's ready to morph, we'll > start the 2.6.x branch. > > i've been thinking about this a lot. rewriting ganglia was the wrong > way to go i think. you're going to instead so our current base morph > into a better piece of software. i want the transition to be a smooth > as possible instead of dramatically changing everything and forcing > people who use ganglia to relearn everything. It might be nice if we could branch sooner rather then later so you can work in the cvs tree and the rest of us can see it. Massive rewrites should probably be discussed before commiting since CVS doesn't really work well in a "commit early, commit often" mode. If a big reorganization is done and then backed out, you get a really weird looking repository. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
pgpg0kgBgvh1Q.pgp
Description: PGP signature
