Re: [Ganglia-developers] 3.3.5 tagged
From: Bernard Li bern...@vanhpc.org To: Daniel Pocock dan...@pocock.com.au Cc: ganglia-developers@lists.sourceforge.net ganglia-developers@lists.sourceforge.net; Carlo Marcelo Arenas Belon care...@sajinet.com.pe Sent: Tuesday, March 27, 2012 10:24 PM Subject: Re: [Ganglia-developers] 3.3.5 tagged 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. Cheers Martin On Tuesday, March 27, 2012, Daniel Pocock dan...@pocock.com.au wrote: On 27/03/2012 16:52, Carlo Marcelo Arenas Belon wrote: On Mon, Mar 26, 2012 at 04:50:18PM +0100, Daniel Pocock wrote: Release 3.3.5 The release has now been tagged in git commit = 9db9beea062c7ce5e5b4d10ed553c9b7cea7642e wrong bundle : carenas@dell ~/src/git/ganglia $ git describe --tags 3.3.5 carenas@dell ~/src/git/ganglia $ cd web/ carenas@dell ~/src/git/ganglia/web $ git describe --tags 3.3.2-3 while web has since had a lot more fixes added as shown by : carenas@dell ~/src/git/ganglia-web $ git describe --tags 3.3.4-14-g7383ed8 carenas@dell ~/src/git/ganglia-web $ git diff --stat 3.3.2-3.. | cat Makefile | 2 +- api/host.php | 9 ++--- cluster_view.php | 4 ++-- functions.php | 15 +++ graph.php | 5 +++-- header.php | 1 + inspect_graph.php | 4 ++-- templates/default/views_view.tpl | 16 8 files changed, 42 insertions(+), 14 deletions(-) Does this result in any actual breakage: does 3.3.5 break anything that was working in 3.3.1 or 3.3.0? If the answer to that question is `no', then we ignore this issue and 3.3.5 continues to be the release candidate. Are these all fixes that belong in the 3.3.x release, or are some of them features that belong in 3.4.x? I am not automatically increasing the pointer to the web submodule because I think that only crucial things should be accepted in 3.3.x releases from now on - the alternative is that a) we freeze the web repo against all non-essential commits until the release is finally finished b) I update the pointer to the web repo on every 3.3.x release attempt -- 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 -- 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 -- 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
Re: [Ganglia-developers] 3.3.5 tagged
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
Re: [Ganglia-developers] 3.3.5 tagged
On Mon, Mar 26, 2012 at 04:50:18PM +0100, Daniel Pocock wrote: Release 3.3.5 The release has now been tagged in git commit = 9db9beea062c7ce5e5b4d10ed553c9b7cea7642e wrong bundle : carenas@dell ~/src/git/ganglia $ git describe --tags 3.3.5 carenas@dell ~/src/git/ganglia $ cd web/ carenas@dell ~/src/git/ganglia/web $ git describe --tags 3.3.2-3 while web has since had a lot more fixes added as shown by : carenas@dell ~/src/git/ganglia-web $ git describe --tags 3.3.4-14-g7383ed8 carenas@dell ~/src/git/ganglia-web $ git diff --stat 3.3.2-3.. | cat Makefile |2 +- api/host.php |9 ++--- cluster_view.php |4 ++-- functions.php| 15 +++ graph.php|5 +++-- header.php |1 + inspect_graph.php|4 ++-- templates/default/views_view.tpl | 16 8 files changed, 42 insertions(+), 14 deletions(-) Carlo -- 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
Re: [Ganglia-developers] 3.3.5 tagged
On 27/03/2012 16:52, Carlo Marcelo Arenas Belon wrote: On Mon, Mar 26, 2012 at 04:50:18PM +0100, Daniel Pocock wrote: Release 3.3.5 The release has now been tagged in git commit = 9db9beea062c7ce5e5b4d10ed553c9b7cea7642e wrong bundle : carenas@dell ~/src/git/ganglia $ git describe --tags 3.3.5 carenas@dell ~/src/git/ganglia $ cd web/ carenas@dell ~/src/git/ganglia/web $ git describe --tags 3.3.2-3 while web has since had a lot more fixes added as shown by : carenas@dell ~/src/git/ganglia-web $ git describe --tags 3.3.4-14-g7383ed8 carenas@dell ~/src/git/ganglia-web $ git diff --stat 3.3.2-3.. | cat Makefile |2 +- api/host.php |9 ++--- cluster_view.php |4 ++-- functions.php| 15 +++ graph.php|5 +++-- header.php |1 + inspect_graph.php|4 ++-- templates/default/views_view.tpl | 16 8 files changed, 42 insertions(+), 14 deletions(-) Does this result in any actual breakage: does 3.3.5 break anything that was working in 3.3.1 or 3.3.0? If the answer to that question is `no', then we ignore this issue and 3.3.5 continues to be the release candidate. Are these all fixes that belong in the 3.3.x release, or are some of them features that belong in 3.4.x? I am not automatically increasing the pointer to the web submodule because I think that only crucial things should be accepted in 3.3.x releases from now on - the alternative is that a) we freeze the web repo against all non-essential commits until the release is finally finished b) I update the pointer to the web repo on every 3.3.x release attempt -- 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
Re: [Ganglia-developers] 3.3.5 tagged
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 On Tuesday, March 27, 2012, Daniel Pocock dan...@pocock.com.au wrote: On 27/03/2012 16:52, Carlo Marcelo Arenas Belon wrote: On Mon, Mar 26, 2012 at 04:50:18PM +0100, Daniel Pocock wrote: Release 3.3.5 The release has now been tagged in git commit = 9db9beea062c7ce5e5b4d10ed553c9b7cea7642e wrong bundle : carenas@dell ~/src/git/ganglia $ git describe --tags 3.3.5 carenas@dell ~/src/git/ganglia $ cd web/ carenas@dell ~/src/git/ganglia/web $ git describe --tags 3.3.2-3 while web has since had a lot more fixes added as shown by : carenas@dell ~/src/git/ganglia-web $ git describe --tags 3.3.4-14-g7383ed8 carenas@dell ~/src/git/ganglia-web $ git diff --stat 3.3.2-3.. | cat Makefile |2 +- api/host.php |9 ++--- cluster_view.php |4 ++-- functions.php| 15 +++ graph.php|5 +++-- header.php |1 + inspect_graph.php|4 ++-- templates/default/views_view.tpl | 16 8 files changed, 42 insertions(+), 14 deletions(-) Does this result in any actual breakage: does 3.3.5 break anything that was working in 3.3.1 or 3.3.0? If the answer to that question is `no', then we ignore this issue and 3.3.5 continues to be the release candidate. Are these all fixes that belong in the 3.3.x release, or are some of them features that belong in 3.4.x? I am not automatically increasing the pointer to the web submodule because I think that only crucial things should be accepted in 3.3.x releases from now on - the alternative is that a) we freeze the web repo against all non-essential commits until the release is finally finished b) I update the pointer to the web repo on every 3.3.x release attempt -- 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 -- 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
[Ganglia-developers] 3.3.5 tagged
Release 3.3.5 The release has now been tagged in git commit = 9db9beea062c7ce5e5b4d10ed553c9b7cea7642e Filename: ganglia-3.3.5.tar.gz SHA256 checksum: 8934ca140cdeef1f3216d8276e18c7f9be5724ca80335fc9bc8b7e2abe55af34 It is still on the pre-release page on Sourceforge, if no problems are found in the next 7 days then it can become the official release. https://sourceforge.net/projects/ganglia/files/pre-release/ -- 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
