Greetings,

while looking at a fix for the broken gmond in at least some of the BSD
platforms that was reported here :

  
http://www.mail-archive.com/ganglia-developers@lists.sourceforge.net/msg05366.html

noticed also that the STATUS file for the 3.1 branch had some confusing
history and which I assume based on our own wiki [1] and a sample file
from apache [2] (which was used as a basis for that) should be instead
something like :

Index: STATUS
===================================================================
--- STATUS      (revision 2122)
+++ STATUS      (working copy)
@@ -7,9 +7,10 @@
 
 Release history:
 
-    3.1.5(hargrave)   : Released: In Development
-    3.1.4(???)        : Released: Not released
-    3.1.3(avenger)    : Released: Not released
+    3.1.6(hargrave)   : In Development
+    3.1.5(hargrave)   : Tagged: Nov 24, 2009
+    3.1.4(hargrave)   : Tagged: Oct 26, 2009 (not released)
+    3.1.3(avenger)    : Tagged: Sep 19, 2009 (not released)
     3.1.2(langley)    : Released: Feb 17, 2009
     3.1.1(wien)       : Released: Sep 10, 2008
     3.1.0(amelia)     : Released: Jul 30, 2008

the main differences and points for discussion being :

* Until we get rid of the release names, and unless the release name
  changes it should be considered that the release name is the same (as
  reported during configure).
* 3.1.3, 3.1.4 and 3.1.5 were released at least as betas and therefore
  the last version of that file misses that information.
* 3.1.3 and 3.1.4 status of "not released" used to be "no GA" and that
  might a better way to identify releases that went through beta cycles
  but never went to GA.
* 3.1.5 is either Released (included tagging and a beta package) or
  in development and since there was an announcement for testing I
  assume is at least in the same state than 3.1.3 and 3.1.4 were, and
  the fact that the GANGLIA_NANO_VERSION and GANGLIA_SNAPSHOT settings
  wasn't updated to reflect that was probably just an oversight which
  has been corrected in r2123
* 3.1.6 has no commits yet but should be open for development at least
  for bugfixes for 3.1.5 (if that gets scrapped) or to include other
  features/bugfixes which had been otherwise on halt since the feature
  freeze for avenger was called.

in any case, looking forward for comments on this so that the fixes (if
needed) can be committed but specially so it is clear on how to proceed
until the GA status for 3.1.5 is decided.

Carlo

[1] http://sourceforge.net/apps/trac/ganglia/wiki/how_project_works
[2] 
http://svn.apache.org/viewvc/httpd/httpd/branches/2.0.x/STATUS?revision=882861&view=markup

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Ganglia-developers mailing list
Ganglia-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to