-
Notifications
You must be signed in to change notification settings - Fork 37
/
Copy pathRELEASE
69 lines (58 loc) · 4.24 KB
/
RELEASE
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
Perform the following steps to release a new version of the plugin on wordpress.org:
1. It might already be too late, but make sure you've read README.md
2. Update the version in tiny-compress-images.php and src/class-tiny-plugin.php
3. Change the 'Stable tag' in readme.txt to the new release number.
4. Add release notes to readme.txt.
5. If you've changed the plugin to work with newer version of WordPress add that to the readme.txt as well.
6. Commit and push to GitHub.
7. Create a new release in Github and create a tag with the new version.
8. Locally, checkout the new tag: `git checkout <tagged version>`.
9. If not already done so, checkout the Subversion repository (outside of your Github repo): `svn co http://plugins.svn.wordpress.org/tiny-compress-images`.
10. If Subversion repo already existed: run `svn update` inside repo `tiny-compress-images`.
11. Update svn:ignore property of trunk when .gitignore is updated: `svn propedit svn:ignore trunk`. Make sure src/vendor/\* is NOT ignored in SVN.
12. Delete everything in trunk `rm -rf <path-to-local-svn-repo/trunk/*`.
13. Manually copy the Git release to the local Subversion repo: run following command under your Github repo: `git ls-files | xargs tar c | tar x -C <path-to-local-svn-repo>/trunk/`.
14. Go back to your svn repo and add new files `svn st | awk '/^\?/ { print $2; }' | xargs svn add`.
15. Delete deleted files: `svn st | awk '/^!/ { print $2; }' | xargs svn rm`.
16. To double check changes to the repo, check difference with `svn status`.
17. Commit the trunk to Subversion: `svn ci -m "<message>"`.
18. Tag the new release in Subversion and commit: `svn cp trunk tags/<version> && svn ci -m "<message>"`.
19. If a tag had been wrongly uploaded, use this line to delete it: `svn delete http://plugins.svn.wordpress.org/tiny-compress-images/tags/<version you want to delete> --message "<message>"`
20. Visit https://translate.wordpress.org/projects/wp-plugins/tiny-compress-images and add the missing translations.
Perform the following steps to make changes to the plugin page on wordpress.org:
1. Make the desired changes in the readme.txt file.
2. Commit and push to GitHub.
3. Checkout the trunk of the Subversion repository.
4. Add the updated readme.txt and Commit the changes to the trunk.
5. Visit https://translate.wordpress.org/projects/wp-plugins/tiny-compress-images and add any missing translations.
6. Checkout the latest tag of the Subversion repository (e.g. 2.2.6).
7. Add the updated readme.txt and Commit the changes again.
8. See the changes (almost immediately) on https://wordpress.org/plugins/tiny-compress-images/
Perform the following steps to change the "Tested up to wordpress version" on wordpress.org:
1. Check if the plugin is compatible with the latest version of WordPress.
2. Make the changes to readme.txt. Only the major version needs to be specified (e.g. "Tested up to: 4.9").
3. Commit and push to GitHub.
4. Checkout the latest tag of the Subversion repository (e.g. 2.2.6).
5. Add the updated readme.txt and Commit the changes.
Increase “Tested up to” Value for WordPress Plugin without making a new release:
Step 1: Thoroughly test the plugin on the new version of wordpress.
(Only proceed with these steps if all still works. If not, fix the issue and make a new release instead).
Step 2: Get Your Subversion Repository URL
This URL is available on the Developers tab of the plugin on wordpress.org in the Subversion Repository link.
"check out the SVN repository"
TinyPNG SVN link: https://plugins.svn.wordpress.org/tiny-compress-images/
Step 3: Make a Local Copy of the Subversion Repo
svn co https://plugins.svn.wordpress.org/tiny-compress-images/
Navigate into your plugin directory with something like
`cd tiny-compress-images`
Step 4: Make a Local Copy of the Subversion Repo
You should updated the “Tested up to” value in your latest tagged release.
Look in tags/ and find the latest version.
If you want to edit this from the command line, you can use:
`nano tags/X.X.X/readme.txt`
You can review the change by using `svn diff`
Step 5: Push the changes back to wordpress.org
You then upload the changes to live, include a message of the change.
`svn ci -m "Tested up to bumped to XX"`
You will be asked for the username and pasword.
Use username TinyPNG with the password from the vault.