[wp-trac] Re: [WordPress Trac] #6744: Include upgrade warnings in a
read me or other notification system
WordPress Trac
wp-trac at lists.automattic.com
Wed Apr 16 13:26:54 GMT 2008
#6744: Include upgrade warnings in a read me or other notification system
-------------------------+--------------------------------------------------
Reporter: hexley | Owner: anonymous
Type: enhancement | Status: new
Priority: normal | Milestone: 2.7
Component: General | Version: 2.5
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Changes (by MichaelH):
* type: defect => enhancement
Comment:
The development blog does try to inform users of most changes. But, it is
quite a job to describe ALL the changes to functionality in a release,
especially for major releases such as 2.5. Some features, changes, and
bug fixes, just get lost in the glitz of all the other 'stuff'.
During the development cycle it is helpful to read
[http://westi.wordpress.com/ Peter Westwood] and his weekly digest of
changes made to WordPress trunk.
Belonging to the [http://lists.automattic.com/mailman/listinfo/wp-trac
Trac email list] is useful for keeping up with all the Trac activity.
Subscribers to that email list saw several emails in February about the
behavior change to 'the more' in feeds (Ticket: #2582).
For the interested users, belonging to the
[http://lists.automattic.com/mailman/listinfo/wp-testers Testers email
list], and the [http://lists.automattic.com/mailman/listinfo/wp-hackers
Hackers email list], can provide a continuing glimpse of what's happening
on 'the development scene.'
In the past, in Codex, a huge effort went into documenting the new
features with each release. Lloyd Budd, in particular, spent quite a bit
of time fleshing out the details for
[http://codex.wordpress.org/Version_2.3 Version 2.3]. There is a
[http://codex.wordpress.org/Version_2.6 Version 2.6 article] that will
need some love. Hopefully, someone will take ownership of that article
and expand it as features are added or changed.
Conclusion:
-1 for adding a readme file to the distribution. The development blog
just feels like the best place for this kind of information. Users that
would, or could, access a readme file, are likely the same users that
follow the community email lists.
--
Ticket URL: <http://trac.wordpress.org/ticket/6744#comment:1>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list