[wp-hackers] Plug-in Repository Structure

[Chip Bennett]

Personally, I use /trunk for my unstable/development version, and only tag
stable versions.

As far as I know, as long as /trunk/readme.txt points to a valid /tag/
version, you shouldn't *have* to maintain anything else in /trunk.

Chip

On Wed, Mar 2, 2011 at 5:14 PM, Eric Mann <eric at eam.me> wrote:

> I want to confirm something before I go off and do it ...
>
> A while ago, I remember someone telling me that the only file you needed in
> the /trunk directory for a plug-in was readme.txt and that it needed to
> point to the appropriate sub-directory for the latest version in /tags.
>
> So ...
>
> my-cool-plugin/
>
> /trunk/
>
> readme.txt
>
> /branches/
>
>  /tags/
>
> /1.0/
>
> readme.txt
> my-cool-plugin.php
>
> /2.0/
>
> readme.txt
> my-cool-plugin.php
> some-other-file.php
>
>
> Is this an accurate description?  Or should the /trunk directory also
> contain the latest stable version in addition to the appropriate version
> folder in /tags?
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>