I'm thrilled that the 1.3 releasenotes has grown up organically --
that everyone's been contributing to it. Unfortunately, I think it's
also hard to understand for average users. It reads like a long TO-DO
list for developers -- which is exactly how we've been using it! Too
much information listed in no particular order.
Having the 10,000-foot perspective that results from spending 8 hours
writing the CHANGES entry, I'd like to reformat the 1.3 releasenotes
file to look like the 1.2 releasenotes. That is: impose some
hiearchy and prioritization. The 1.2 notes have a quick summary at
the top, and a *prioritized* list of details down below. Assuming
nobody objects strongly, I'm going to do the same now for the 1.3
notes...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 14 21:05:04 2005