![]() ![]() The increment in the version will force WordPress to recognize the update and provide the fix to anyone who's already installed version 2.2. I'll do a quick patch and immediately release 2.2.1. Let's say I've released version 2.2 of a plugin and someone notices I forgot to invoke jQuery in noConflict() mode. If I notice a bug in a live version, I'll make a quick patch and release a maintenance version. you'll almost never see a build number from me unless I manually email you a file (it's how I can distribute pre-release versions that won't break WordPress updates). 5īuild numbers I only ever use internally or for beta releases. I typically following this kind of versioning schema: 2. If you need to make a minor change, consider it a maintenance release. I recommend you release a version 3.0 next, then be very careful when versioning in the future to prevent this kind of typo. A standard PHP version comparison will see version 2.81.2 as being a newer version than 2.9 because 81 > 9. If you committed version 2.81.2 as an update and people actually downloaded that update, they won't see 2.9 when you release it.Įxactly. Commit the entire plugin to save the tagīingo.Right click /trunk and create a new tag, copying into /tags/X.X.X where x.x.x is the same version in the "stable" tag of readme.txt (step 2).Commit the entire plugin to save the changes to /trunk to the repository.Copy your local updates into the /trunk directory of the local plugin folder.Increment the "stable" tag in your readme.txt file to match the new version number.Code the plugin updates locally until you're happy with it.What do I edit and commit to make any new downloads of the plugin contain the change?ĭo I have to edit the trunk AND the tag folder and commit both?ĭon't be. If I spot a silly mistake in the code that doesn't really affect the working of the plugin, maybe a typo or an additional image. 2.9.2 is considered a lower version than 2.81.2 ? (because, as I understand it, version_compare starts at the left and compares higher/lower for each digit so 9 would be considered less than 81) How does wordpress determine which is the latest version and if the user should update their version? does it do a version_compare ? that only works with proper php version format doesn't it? eg. Is that correct and in the right order? if not, what is the correct way?įor some reason, I went from version 2.8.1 to 2.81.2 on my last update, does this mean that it wont show as an update available in the dashboards of people that have version 2.81.2 if I change the next version number to 2.9 ? right click the trunk directory and choose create branch/tag and set it to copy to a folder in /tags/ with the name being the version number.copy over all the files inside my local plugin folder to the /trunk/ (the plugin and readme file have updated version numbers). ![]() code the plugin updates on my local until I'm happy with it.Somehow I've managed so far but I need to know the proper procedure for updating my plugin to the new version with regards to committing the trunk and making a tags directory. There's a lot of questions about svn here but they've only confused me further :-z ![]() ![]() * svn co svn://some.machine/book ~/book(note that capitalization is important on Linux)I'm embarrassed to say that I am a bit clueless on the procedure used to update a plugin via tortoise svn even though my plugin has been on the repository for years and had over 300,000 downloads!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |