[wp-hackers] Plug-in Repository Structure
eric at eam.me
Thu Mar 3 15:47:02 UTC 2011
> The correct process is:
> Commit changes to trunk.
> Commit more changes to trunk
> Test trunk
> Tag trunk
> Update readme.txt in trunk to point to new stable tag.
> The important thing is that the readme.txt in trunk should always reference
> a tag which already exists and is checked in.
My problem with that process is that it means you have to maintain
readme.txt separately from everything else. Particularly if you use the
repository to host in-development version of plug-ins ... I'd hate to have a
half-developed release referenced in the FAQs of the readme. That would
just further confuse people.
More information about the wp-hackers