Skip to content

Commit 86bfc3d

Browse files
committed
Upgrade version number to 3.1.2
And update notes on releasing a new version.
1 parent e754dec commit 86bfc3d

File tree

3 files changed

+18
-9
lines changed

3 files changed

+18
-9
lines changed

CHANGES

+7
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,13 @@ most recent build should be at the top of this file.
88

99
Thanks!
1010

11+
3.1.2
12+
-----
13+
- More crash fixes
14+
- Fix Vienna forgetting current folder/feed after termination and relaunch
15+
- Restore mechanism required by some plugins, especially "Add to Safari reading list"
16+
- Conversion to modern Ojective-C
17+
1118
3.1.1
1219
-----
1320
- Fix some crashes

Release Instructions.txt

+6-5
Original file line numberDiff line numberDiff line change
@@ -57,11 +57,12 @@ Tags should be in one of the following formats:
5757
11. Check your email and verify that you have a message from Sourceforge stating "GitHub Downloads Import Complete".
5858
12. Verify the downloads. Load the SourceForge Downloads page for Vienna at <https://sourceforge.net/projects/vienna-rss/files/>, download new zip files, uncompress them, and run the apps.
5959
13. For stable releases only : from the Sourceforge site, edit the "Properties" of "Vienna3.1.0.tgz" and set it as default download for Mac OS X. Don't do this for beta releases!
60-
14. Login to the Vienna web site directory with your admin account. `sftp <username>@web.sourceforge.net` where `<username>` is your SourceForge user name.
61-
15. Upload `changelog_beta.xml` (or `changelog_rc.xml` or `changelog.xml` accordingly) and the `noteson3.1.0_beta4.html` file via sftp to `/home/project-web/vienna-rss/htdocs`.
62-
16. If you upload a release candidate, change changelog_beta.xml to be a copy of the new changelog_rc.xml ; and if you upload a release, change changelog_rc.xml to be a copy of the new changelog.xml
63-
17. Ensure that these files are set to be group writable.
64-
18. Run the previous version of Vienna, and make sure that the Sparkle update mechanism works correctly to display and download the latest version. After updating, check again to make sure Sparkle is showing that you have the latest version.
60+
61+
## On viennarss.github.io
62+
63+
14. Upload `changelog_beta.xml` (or `changelog_rc.xml` or `changelog.xml` accordingly) and the `noteson3.1.0_beta4.html` file in the sparkle_files directory
64+
15. If you upload a release candidate, change changelog_beta.xml to be a copy of the new changelog_rc.xml ; and if you upload a release, change changelog_rc.xml to be a copy of the new changelog.xml
65+
16. Run the previous version of Vienna, and make sure that the Sparkle update mechanism works correctly to display and download the latest version. After updating, check again to make sure Sparkle is showing that you have the latest version.
6566

6667
Finally, consider posting an announcement of the new release on the CocoaForge Vienna forum at <http://forums.cocoaforge.com/viewforum.php?f=18> and/or <http://vienna-rss.org>.
6768

notes.html

+5-4
Original file line numberDiff line numberDiff line change
@@ -107,12 +107,13 @@
107107

108108
<h1 id="toc_0">Version Notes</h1>
109109

110-
<h2 id="toc_1">3.1.1</h2>
110+
<h2 id="toc_1">3.1.2</h2>
111111

112112
<ul>
113-
<li>Fix some crashes</li>
114-
<li>Fix deadlocks on OS X 10.8</li>
115-
<li>Fix the sort functionality in Activity Window</li>
113+
<li>More crash fixes</li>
114+
<li>Fix Vienna forgetting current folder/feed after termination and relaunch</li>
115+
<li>Restore mechanism required by some plugins, especially &ldquo;Add to Safari reading list&rdquo; </li>
116+
<li>Conversion to modern Ojective-C</li>
116117
</ul>
117118

118119

0 commit comments

Comments
 (0)