[wp-hackers] Adding a plugins svn committer

Dan Phiffer dan at phiffer.org
Fri Oct 7 17:01:04 UTC 2011

Thanks Mike, I appreciate all the positive feedback with the plugin! And I agree that there's a kind of chilling effect introduced by more adding complexity to code submissions.

Broadening the coverage of my tests is always a good idea, and introducing specific cases I personally depend on is an especially good idea. Security-wise I'm starting to think that the risk is actually not very substantial since I'm the only one hitting the upgrade button on my WP installs. I'm going to stick with Subversion and adopt a Reagan-style "trust but verify" motto.


On Oct 7, 2011, at 4:56 AM, Mike Bijon wrote:

> @Dan,
> A lot of these options could work, but they reduce risk by limiting
> contributions. Why not open the SVN repo up but add an extra layer of
> testing on your end? Then you could facilitate contributions & upgrades, but
> still confirm if upgrades would be safe.
> Automated testing isn't common for WP plugins, but you should be able to
> implement a few tests specifically to confirm your transactions will keep
> working.
> ---
> BTW Dan, I've used your JSON API plugin twice on sites. Great system, thank
> you.
> _______________________________________________
> 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