Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=4OT4qBRy462WKkEkD69fbDyqeoi3BTaCpok7CyEoeCVDpwBnJN9vzYFc8wKRF4xoiY7SG1tFJ0I2EsjtaGLBy8VGil3GnHGQfsZLHl7JLtmU3BPF6tw/u0cHqlIensowU9ouKJNComA++6bbw0Zu5nn/I6MjXByvaC4QKkTd/nM=;
References: <1328197100.96201.YahooMailNeo@web160905.mail.bf1.yahoo.com>
 <CAGaRif2xY-w+A-LhRBKAHN38izVaVRy5ru2Y6+W4KAeiBw_geQ@mail.gmail.com>
Message-ID: <1328199853.66040.YahooMailNeo@web160902.mail.bf1.yahoo.com>
Date: Thu, 2 Feb 2012 08:24:13 -0800 (PST)
From: Joe Schaefer <joe_schaefer@yahoo.com>
Reply-To: Joe Schaefer <joe_schaefer@yahoo.com>
Subject: Re: last release date in reports?
To: Lewis John Mcgibbney <lewis.mcgibbney@gmail.com>,
  "general@incubator.apache.org" <general@incubator.apache.org>
In-Reply-To: 
 <CAGaRif2xY-w+A-LhRBKAHN38izVaVRy5ru2Y6+W4KAeiBw_geQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="498176207-1764503219-1328199853=:66040"

--498176207-1764503219-1328199853=:66040
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Personally that's probably a wee bit too much=0Adetail other than to mentio=
n anecdotally.=A0 If=0Athe person who is writing the report perceives=0Apro=
blems with the technical aspects of the project,=0Awe certainly encourage t=
hem to write about it.=0A=0A=0A=0A=0A>________________________________=0A> =
From: Lewis John Mcgibbney <lewis.mcgibbney@gmail.com>=0A>To: general@incub=
ator.apache.org; Joe Schaefer <joe_schaefer@yahoo.com> =0A>Sent: Thursday, =
February 2, 2012 11:22 AM=0A>Subject: Re: last release date in reports?=0A>=
 =0A>=0A>Hi Joe,=0A>=0A>I don't know if this is as fundamental as the 'last=
 release date' issue you raise, but it might be also advantageous to the bo=
ard for (especially) podlings to mention whether trunk is broken or not. In=
 the past I've seen some podlings with trunk broken for some time and altho=
ugh in some cases this might be something trivial, in other cases it can me=
an that there is something more severe at play and the board may wish to kn=
ow an accurate snapshot representation of the project when reporting is due=
.=0A>This is just my personal opinion, and I know it is not paramount, but =
it creates a layer of transparency which I think could really help mentors =
as well as the Board to comment accordingly.=0A>=0A>Thanks=0A>=0A>Lewis=0A>=
=0A>=0A>On Thu, Feb 2, 2012 at 3:38 PM, Joe Schaefer <joe_schaefer@yahoo.co=
m> wrote:=0A>=0A>I've looked over the reports so far for February=0A>>and a=
m fairly impressed at the quality of them=0A>>compared to January's bunch.=
=A0 OTOH one bit of information=0A>>I'd like to see given more attention is=
 a podling's=0A>>last release date, to see how they are progressing=0A>>tec=
hnically as a community which focuses on producing=0A>>quality software sui=
table for public consumption.=0A>>=0A>=0A>=0A>-- =0A>Lewis =0A>=0A>=0A>=0A>
--498176207-1764503219-1328199853=:66040--