Releases

From Yabause
Revision as of 22:25, 9 June 2013 by Guillaume (Talk | contribs)

Jump to: navigation, search
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

configure.in, /src/c68k/configure.in, /src/makefile.mng, /src/carbon/Yabause.app/Contents/Info.plist, and /src/windows/yabause.vcproj should be using the correct version number

  • 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 cvs

Using regular cvs, go into a shell, make sure you've logged in, and that cvs is up to date. Go in your top cvs directory. Lastly, type: cvs tag -c -- 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 first checking out the tagged CVS: cvs co -r release_X_Y_Z yabause then moving in the yabause directory and untag with cvs tag -d release_X_Y_Z.

Using wincvs, you can just select all the files to tag, then click on the "Modify" menu, and then on "Create a Tag". Once the menu pops up, enter "release_X_Y_Z"(where X, Y, and Z are your version number) in the "New tag name" field. Also make sure that "Check that the files are unmodified before tagging" is checked. Then hit ok.

Windows Build process

Here's a step-by-step process of building the windows port without using msys:

Make sure version number is correct first in /src/makefile.mng Go into the /src directory and type "mingw32-make -f makefile.mng" Zip the exe and don't forget to add the following files: AUTHORS, ChangeLog, COPYING, glut32.dll, mingwm10.dll, README, README.WIN.

Uploading packages to sourceforge

Login to sourceforge, go to the project's page, and click on Admin->File Releases. Here, click on "Add Release" beside the correct package name. Now enter in the release name(should be the version). Click on "Create This Release". Now here you enter in the changelog, a brief note about the changes for the program, and then upload the file to sourceforge's ftp. 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 wordpress login page, login, and at the dashboard, click on "Write a 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 "Releases") and then when you're done click on "Publish". Congrats! You're all done!