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

Reply via email to