[wp-hackers] Plug-in Repository Structure

Chip Bennett chip at chipbennett.net
Thu Mar 3 15:57:57 UTC 2011

Perhaps I'm just slow this morning (it wouldn't be the first time), but I
don't understand the problem.

Say your stable Plugin version is 3.1.

You have plugins.svn.wordpress.org\plugin-slug\tags\3.1\<plugin files>

Then in plugins.svn.wordpress.org\plugin-slug\trunk\ you have:

 - Development versions of <plugin files>
 - Development version of readme.txt, with the header tag "Stable Tag: 3.1"

The Extend readme parser sees the "Stable Tag: 3.1", *quits parsing
\trunk\readme.txt, and begins parsing \tags\3.1\readme.txt*.

So, you can continue to maintain your development version of readme.txt,
without any risk of "development" information being displayed prematurely in


On Thu, Mar 3, 2011 at 9:47 AM, Eric Mann <eric at eam.me> wrote:

> >
> > 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.
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list