>> I thought the original idea was that the "web" component was going to be a >> separate entity and thus can be released at different cycles from the other >> components. If we are again releasing web at the same time as ganglia-core >> then this is back to how things were originally when the code is in SVN. >> >> Just my $0.02. >> >> Cheers, >> >> Bernard >> > > Add my coins to that. Wanted to write the same. Just lets be progressive > and split out the WEB part from the data collection part and let them move at > their own pace. That cross project link in the repo is most confusing anyway.
I don't think we should go back the way things were, but there are other ways we can move forward: a) ganglia-web becomes fully independent again: but it jumps ahead to become v3.4, so that people using Debian, Fedora, etc can upgrade ganglia-web-3.1 -> ganglia-web-3.4 seamlessly: - simultaneously release a ganglia-3.4.x.tar.gz that has no web directory, to emphasize that the new web UI is the `one and only' - releases of ganglia-3.3.x will continue to have the web stuff, but with no new features (just essential bug fixes, maintained on a branch) b) I ruthlessly simplify the release process, so web releases can come whenever new features are ready: - kill off libmetrics/configure - kill off web/Makefile - merge both the monitor-core and web repo into a single repo (preserving history) - do everything from the main configure/make in one go - remove a lot of the logic from main configure, and force people building packages to set things like LDFLAGS manually (this is actually autoconf best practice, it also means less responsibility for the official Ganglia packages to try and be all things to all people) - maybe even move some of the non-essential python stuff out of the repo, create standalone packages like ganglia-modules-linux, so that changes to these things don't impact the release cycle My original objective in merging the web stuff was to make it the default and kill off the old UI, to ensure there is only one UI for distributions and packages to worry about, only one UI to be covered in the book, etc. I continue to feel this was a 100% worthwhile objective. However, either plan (a) or (b) above will achieve the same goals, so please cast your votes or propose a plan (c) ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
