It looks good, but as someone trying to avoid CVS I'm not sure I will ever use
One general comment, weekly or daily summaries are nice, but a cumulative list
is even better.
Then someone can review all the activity since the last major release.
You could start a new cumulative list every time a release came out.
If you decide to go that way, I think a ID # would be good to have for each
That way, the experts can tell us, get the xfs 1.1 release with the #1 and #2
patches and see if it fixes your problem.
>> On Fri, 23 Aug 2002, Christoph Hellwig wrote:
>> > I think XFS would really need someone to maintain the website. It's
>> > horribly out of date, and misses some important links. For example
>> > it would be nice to have a link to my XFS merge status or even a
>> > version. I don't know whether externals are allowed to work on
>> > though..
>> Okay, I've been thinking about what I can do and have come up with
>> something along these lines. The mozilla project has a status report
>> which is basically a weekly summary of what people have done. This is
>> different than the merge status report, which is a more overview of what
>> has been done and what lies ahead. I propose to do a (possibly weekly or
>> more often) summary of the TAKE messages so that people know what has been
>> fixed in CVS, similar to the mozilla project's weekly status report.
>> I've put together a very quick example of what I plan to do at:
>> it covers the two checkins today (oops - Steve just checked in a third).
>> Tell me if you think this is a good thing or a waste of time.
>> James Rich
Deployment and Integration Specialist
Compaq ASE - Tru64 v4, v5
Compaq Master ASE - SAN Architect
The Norcross Group