Difference between revisions of "Releases"

From Yabause
Jump to: navigation, search
(Updates)
(Format fixing)
Line 7: Line 7:
  
 
* All source files should have a license header  
 
* All source files should have a license header  
/src/android/AndroidManifest.xml, /src/cocoa/Yabause-Info.plist, /src/cocoa/Yabause.xcodeproj, /src/gtk/doc/yabause.1, /src/Makefile.dc, /src/qt/doc/yabause.1, and /src/qt/scripts/yabause_setup.iss should be using the correct version number
+
* The following files should be using the correct version number:
 +
/src/android/AndroidManifest.xml
 +
/src/cocoa/Yabause-Info.plist
 +
/src/cocoa/Yabause.xcodeproj
 +
/src/gtk/doc/yabause.1
 +
/src/Makefile.dc
 +
/src/qt/doc/yabause.1
 +
/src/qt/scripts/yabause_setup.iss
 
* AUTHORS should be complete and accurate.  
 
* AUTHORS should be complete and accurate.  
 
* README if anything was changed in the compiling process(e.g. new libraries) or if there was any interface changes.  
 
* README if anything was changed in the compiling process(e.g. new libraries) or if there was any interface changes.  

Revision as of 20:20, 27 October 2013

Warning Information on this page is out of date
Yabause Manual
For users
For developers
edit

Things to check

The following things should be checked to make sure they're up to date and correct:

  • All source files should have a license header
  • The following files should be using the correct version number:
/src/android/AndroidManifest.xml
/src/cocoa/Yabause-Info.plist
/src/cocoa/Yabause.xcodeproj
/src/gtk/doc/yabause.1
/src/Makefile.dc
/src/qt/doc/yabause.1
/src/qt/scripts/yabause_setup.iss
  • AUTHORS should be complete and accurate.
  • README if anything was changed in the compiling process(e.g. new libraries) or if there was any interface changes.
  • ChangeLog should be double-checked for accuracy and any things that need adding should be added.

Tagging svn

Using regular svn, go into a shell, make sure you've logged in, and that svn is up to date. Go in your top svn directory. Lastly, type: svn copy svn+ssh://svn.code.sf.net/p/yabause/code/trunk/yabause svn+ssh://svn.code.sf.net/p/yabause/code/tags/release_X_Y_Z/yabause -m "Release X.Y.Z" where X, Y, and Z are your version number. You don't need to commit after tagging a repository.

A tag can be removed by using the following cmd: svn delete svn+ssh://svn.code.sf.net/p/yabause/code/tags/release_X_Y_Z -m "Tag no longer needed"

Specific Ports build notes

Finish me

Uploading packages to sourceforge

Login to sourceforge, go to the project's page, and click on Files. Click on "yabause" here, click on "Add Folder". Now enter in the release name(should be the version). Click on "Create". Now make sure you're in the release's folder and click "Add File". Select the file and press "Upload". Once everything is setup correctly, click on "Submit/Refresh". When everything is ready, set the release to Active and send out an email to the users that subscribed.

Updating the website

Basically there's two main things that need to be done. The first thing is updating the download page.... which I'll get to another time.

The second thing is that a news post has to be submitted using wordpress. Basically go to the yabause wordpress login page, login, and at the dashboard, click on "New"->"Post". The rest should be pretty simple. Just enter a title for the post, the post itself, make sure the category is checked(should be "Release") and then when you're done click on "Publish"(or "Save Draft" if you're not ready to publish). Congrats! You're all done!