Comments on: Share your plugins on WordPress.org http://idealienstudios.com/blog/tutorials/share-your-plugin-on-wordpress/ We will turn your dreams into reality together! Mon, 19 Jul 2010 08:40:14 +0000 hourly 1 By: Jamie http://idealienstudios.com/blog/tutorials/share-your-plugin-on-wordpress/comment-page-1/#comment-243 Jamie Wed, 11 Nov 2009 14:57:40 +0000 http://idealienstudios.com/?p=233#comment-243 Thanks Rodolfo. Short answer is that in order to have your plugins show up in wordpress.org extend / plugins gallery, you must use their SVN repository. But for other pieces of code...If you are very organized with your digital materials and working in isolation on a project, a system like SVN "isn't" specifically required. You could use Dreamweaver to FTP your files to the server, make copies of the entire code base before you make any changes and "effectively" manually track versions if you want. However, a version management system like SVN makes that process a lot easier once you get familiar with it. It also takes up a lot less time / disk space once you do start to use it - not to mention the benefits which come when you are working on a project collaborating with other developers. I'm sure others would have different opinions on the matter, but once I get beyond the alpha concept stage for any code, I usually setup a repository of some form so that the code base is not entirely dependant on me (and one hard drive). Thanks Rodolfo. Short answer is that in order to have your plugins show up in wordpress.org extend / plugins gallery, you must use their SVN repository. But for other pieces of code…If you are very organized with your digital materials and working in isolation on a project, a system like SVN “isn’t” specifically required. You could use Dreamweaver to FTP your files to the server, make copies of the entire code base before you make any changes and “effectively” manually track versions if you want.

However, a version management system like SVN makes that process a lot easier once you get familiar with it. It also takes up a lot less time / disk space once you do start to use it – not to mention the benefits which come when you are working on a project collaborating with other developers. I’m sure others would have different opinions on the matter, but once I get beyond the alpha concept stage for any code, I usually setup a repository of some form so that the code base is not entirely dependant on me (and one hard drive).

]]> By: Rodolfo http://idealienstudios.com/blog/tutorials/share-your-plugin-on-wordpress/comment-page-1/#comment-242 Rodolfo Wed, 11 Nov 2009 05:52:36 +0000 http://idealienstudios.com/?p=233#comment-242 Great tutorial, it goes directly to the objective of sharing in wordpress. But I am a little unsure about what is SVN and if I could implement a technique like this with my other pieces of code. Can Dreamweaver also work with a remote repository in you server, for example ? Thanks a lot ! Great tutorial, it goes directly to the objective of sharing in wordpress. But I am a little unsure about what is SVN and if I could implement a technique like this with my other pieces of code. Can Dreamweaver also work with a remote repository in you server, for example ?

Thanks a lot !

]]> By: Jamie http://idealienstudios.com/blog/tutorials/share-your-plugin-on-wordpress/comment-page-1/#comment-104 Jamie Wed, 17 Jun 2009 19:36:44 +0000 http://idealienstudios.com/?p=233#comment-104 Thanks for the comment Dave. I've updated the trunk, tag, branch descriptions so that it is a little clearer. Thanks for the comment Dave. I’ve updated the trunk, tag, branch descriptions so that it is a little clearer.

]]> By: Dave Doolin http://idealienstudios.com/blog/tutorials/share-your-plugin-on-wordpress/comment-page-1/#comment-103 Dave Doolin Wed, 17 Jun 2009 18:17:28 +0000 http://idealienstudios.com/?p=233#comment-103 You do not have to tag every commit to trunk. In fact, you shouldn't, it's redundant. Tag when you release. Big difference. There is something funny in how wordpress.org is scripting the releases with respect to tags. I'm going to have to dig out the script to see exactly what they are doing. But in general, develop in trunk and increment your version independently. When you're ready to release, then update your readme.txt and make a tagged copy. Or use a branch, then merge into trunk, update version, copy to tags for release. You do not have to tag every commit to trunk. In fact, you shouldn’t, it’s redundant.

Tag when you release.

Big difference.

There is something funny in how wordpress.org is scripting the releases with respect to tags. I’m going to have to dig out the script to see exactly what they are doing.

But in general, develop in trunk and increment your version independently. When you’re ready to release, then update your readme.txt and make a tagged copy. Or use a branch, then merge into trunk, update version, copy to tags for release.

]]> By: Ber2 http://idealienstudios.com/blog/tutorials/share-your-plugin-on-wordpress/comment-page-1/#comment-95 Ber2 Mon, 15 Jun 2009 03:45:32 +0000 http://idealienstudios.com/?p=233#comment-95 Great article. Thanks for the sharing. Great article. Thanks for the sharing.

]]>