Hi Brad: [I've changed the subject line to be more reflective of the current discussions]
On Thu, Nov 4, 2010 at 8:50 AM, Brad Nicholes <bnicho...@novell.com> wrote: > I'm not sure that we need to physically split the web frontend from the > backend as far as the Ganglia project goes. IMO, why not just follow the > pattern that we already have in SVN under trunk. Right now we have > trunk/monitor-core which includes everything. Could we just create a new > directory under trunk called web-frontend and move everything that has to do > with the web frontend out of monitor-core and into web-frontend. From that > point on, they could both be treated as separate projects with their own > release cycles without physically splitting the code into different > repositories. Tagging and branches would also work the same way. That's fine. How about versioning? Or am I thinking too much? One potential issue is that ganglia-core would be at 4.0 and ganglia-web will be at 3.5 -- this might cause confusion as to what combination is supported, or vice versa. Cheers, Bernard ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
