Personally that's probably a wee bit too much detail other than to mention anecdotally. If the person who is writing the report perceives problems with the technical aspects of the project, we certainly encourage them to write about it.
>________________________________ > From: Lewis John Mcgibbney <lewis.mcgibb...@gmail.com> >To: general@incubator.apache.org; Joe Schaefer <joe_schae...@yahoo.com> >Sent: Thursday, February 2, 2012 11:22 AM >Subject: Re: last release date in reports? > > >Hi Joe, > >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 board 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 although in some cases this might >be something trivial, in other cases it can mean that there is something more >severe at play and the board may wish to know an accurate snapshot >representation of the project when reporting is due. >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. > >Thanks > >Lewis > > >On Thu, Feb 2, 2012 at 3:38 PM, Joe Schaefer <joe_schae...@yahoo.com> wrote: > >I've looked over the reports so far for February >>and am fairly impressed at the quality of them >>compared to January's bunch. OTOH one bit of information >>I'd like to see given more attention is a podling's >>last release date, to see how they are progressing >>technically as a community which focuses on producing >>quality software suitable for public consumption. >> > > >-- >Lewis > > > >
