[wp-testers] SVN for plugins?

[Tris Hussey]

Thank you Frederick, I was wondering about that. Maybe it's a pie in the sky
"when I have the time" thing to do, but at least I've learned a lot about
svn:externals in the process!

Cheers, Tris

On Tue, Mar 9, 2010 at 3:15 PM, Frederick Ding <frederick.ding at live.ca>wrote:

> [Plugin Name]/trunk/ is usually the current *development* version of a
> plugin. As a plugin developer, I will sometimes commit changes NOT YET
> READY
> for release in the /trunk/ folder for a plugin.
>
> The WordPress.org plugin repository builds a zip archive of each plugin
> from
> the latest *TAG* specified in the readme.txt file in /trunk/. This is
> usually a reliable indicator of the latest version. Although most plugins
> are released in this way (to take advantage of the auto-update features for
> plugins in WordPress), there may be a few that do not tag their versions
> and
> release the /trunk/ version.
>
> To implement the repository you would like to create, it would be necessary
> to make some sort of script to parse the [Plugin Name]/trunk/readme.txt
> file
> just like the WordPress.org plugin repository does and retrieve the files
> from [Plugin Name]/trunk/[latest tag]/ .
>
> Alternatively, you can use the undocumented WordPress API, which has a
> method specifically for finding plugin updates
> (http://api.wordpress.org/plugins/update-check/1.0/). I don't know how
> it's
> implemented in core, but it looks like plugin updates are queried in
> http://core.trac.wordpress.org/browser/trunk/wp-includes/update.php#L91.
>
> ——
> Regards,
> Frederick Ding   |   frederick.ding at live.ca
>
> -----Original Message-----
> From: Tris Hussey [mailto:tris at trishussey.com]
> Sent: March 9, 2010 04:19
> To: wp-testers at lists.automattic.com
> Subject: Re: [wp-testers] SVN for plugins?
>
> Yeah no kidding. I started checking out the repository with svnX and I
> thought my connection stalled with all the plugins there. It's pretty
> amazing how much is there.
>
> Just from a functional standpoint, is [plugin-name]/trunk/ the current
> released build or one to be released? I see that each plugin has the
> standard trunk, branches, tags setup like the the WP repository. What I'm
> thinking about is making a repository that pulls the updated builds for the
> key plugins I use from the main repository. Since I don't want to have to
> keep using svn switch to change from tag to tag, I'd like see if I can do
> it
> with one url per plugin.
>
> Cheers, T
>
> On Tue, Mar 9, 2010 at 12:41 AM, Brian Layman <Brian at thecodecave.com>
> wrote:
>
> > > Danke. :D ... oh such fun.
> > > Tris
> >
> > The Plugin Repository at
> >
> > http://plugins.svn.wordpress.org/
> >
> > is a wonderful world of learning and inspiration..
> >
> > Want to know how to do something? With this repository checked out,
> > you have an encyclopedia of examples at your fingertips. I wish I knew
> > of a way to check out the whole thing without getting every single tag
> > there ever was, but even that, with a good comparison tool, shows you
> > how to fix security holes.
> >
> > Start it checking out before going to bed one night. Hours of fun will
> > ensue...
> >
> > -brian layman
> >
> >
> > _______________________________________________
> > wp-testers mailing list
> > wp-testers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-testers
> >
>
>
>
> --
> Tris Hussey
> Writer | Teacher | Photographer | Internet Rogue
> cell: 604-319-6765 -- Skype: tris.hussey http://www.trishussey.com/
>
>
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>
>


-- 
Tris Hussey
Writer | Teacher | Photographer | Internet Rogue
cell: 604-319-6765 -- Skype: tris.hussey
http://www.trishussey.com/