[wp-docs] Handling Version Differences in Documentation
Scott Merrill
skippy at skippy.net
Tue Aug 31 19:21:55 UTC 2004
Tor Bjornrud said:
> This all started when I thought about writing up some docs for
> customization, but realized that they would either be obsolete with
> 1.3, or that they wouldn't be relevant now (without proper notes) as I
> use a cvs copy of WordPress locally.
I think there's a sufficient body of users desperate for decent
documentation for the current version, and also a large body of people who
will _not_ be "early adopters" of any new release, that making your
documentation 1.2 specific is a safe bet. Plus, it serves as a good
starting point for a 1.3 version of the same documentation.
I can't imagine older versions of WordPress being _officially_ supported
much past the release of a new version, given the nature of the
application. As such, once the new version is out all previous
documentation could become permanently "historical", and not up for
revision.
All historical docs could either be exported to flat files, and left
available for those that feel they need them.
More information about the docs
mailing list