{"id":420,"date":"2009-07-22T01:32:48","date_gmt":"2009-07-22T05:32:48","guid":{"rendered":"http:\/\/www.rakkar.org\/blog\/?p=420"},"modified":"2009-07-22T01:32:48","modified_gmt":"2009-07-22T05:32:48","slug":"making-raknet-releases-then-vs-now","status":"publish","type":"post","link":"https:\/\/rakkar.org\/blog\/index.php\/2009\/07\/22\/making-raknet-releases-then-vs-now\/","title":{"rendered":"Making RakNet releases, then vs. now"},"content":{"rendered":"

\t\t\t\tThen:<\/strong><\/p>\n

    \n
  1. Rebuild all<\/li>\n
  2. Run a batch file to delete temporary files (.obj, etc.)<\/li>\n
  3. Zip the whole directory<\/li>\n
  4. Add a comment to revisionlog.txt<\/li>\n
  5. Upload it, overwriting the old file (RakNet.zip)<\/li>\n
  6. Change the date on the front page<\/li>\n
  7. If I remember, also change the version number in readme.txt<\/li>\n<\/ol>\n

    It took me about 5 minutes to make a build. As a result, anytime I found a bug I’d basically release a build immediately.<\/p>\n

    Now:<\/strong><\/p>\n

      \n
    1. Rebuild all<\/li>\n
    2. Of the over 50 projects, fix the ones that no longer build<\/li>\n
    3. Fix warnings introduced by various ifdefs<\/li>\n
    4. Build on Code Blocks, adding new files. Fix compile errors\/warnings.<\/li>\n
    5. Build on Dev-cpp, adding new files.<\/li>\n
    6. Go to the source directory, do dir *.h, copy out file list to a text editor. Modify output to match formatting tags for makefiles. Copy output to makefile.<\/li>\n
    7. Do the same for *.cpp<\/li>\n
    8. Do a similar process for the VC6 project (if I bother)<\/li>\n
    9. Build in Visual Studio again to make sure things still build<\/li>\n
    10. Copy source files to CYGWIN. Figure out how to compile in GCC again, and fix any compile errors if any.<\/li>\n
    11. Run through the easier to test projects to make sure the major features still superficially work<\/li>\n
    12. Figure out when the last build was made, look up the log from SVN, and collect all the check-in log entries<\/li>\n
    13. Format the log entries and add them to revisionlog.html. This is non-trivial, to prevent revisionlog from being unreadable<\/li>\n
    14. Change the version number in readme.txt and RakNetVersion.h<\/li>\n
    15. Update the remote dedicated server from SVN, rebuild, and restart<\/li>\n
    16. Generate the Irrlicht demo exe. Download the .zip from the website, update the exe, and reupload<\/li>\n
    17. In SVN, create a tag with the version number, which involves looking up how to do it each time<\/li>\n
    18. Regenerate the Doxygen html documentation<\/li>\n
    19. Run HTML help workshop to generate the chm documentation. Move the chm file out of the html file.<\/li>\n
    20. If I remember, upload the new Doxygen documentation to the website<\/li>\n
    21. Export from SVN to a temp directory.<\/li>\n
    22. Zip the files in the temp directory. Sometimes there are unusual steps here, such as unzipping the ogre sample (lately I don’t bother to do that).<\/li>\n
    23. Upload the zip to Sourceforge<\/li>\n
    24. Figure out how to navigate the Sourceforge interface to get to the new releases page (which takes me a couple of minutes every time)<\/li>\n
    25. Add a new release. Paste in the revision log from earlier. Add the file, and submit.<\/li>\n
    26. Upload the same zip file to the website, making sure the version number of the filename of the zip file is correct.<\/li>\n
    27. Open the 6 different pages on the website that reference the link and update them.<\/li>\n
    28. Update the news page in the forum to point to the correct link<\/li>\n
    29. Add a post to version announcements with the revision log.<\/li>\n
    30. I used to also edit the download graphic with the correct version number. But this got to be such a pain I just changed it to 3.x so I wouldn’t have to keep modifying it.<\/li>\n
    31. Sometimes send a post to gamedev.net about the new release (lately I don’t usually bother).<\/li>\n
    32. Think about which of these steps I forgot, and sometimes redo part of this if I did.<\/li>\n<\/ol>\n

      It takes about an hour to make a build. I do a build every 1-3 months, depending on if I find any major bugs and how stable I feel the code is. If I’m changing existing code every day I usually won’t release.\t\t<\/p>\n","protected":false},"excerpt":{"rendered":"

      Then: Rebuild all Run a batch file to delete temporary files (.obj, etc.) Zip the whole directory Add a comment to revisionlog.txt Upload it, overwriting the old file (RakNet.zip) Change the date on the front page If I remember, also change the version number in readme.txt It took me about 5 minutes to make a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/rakkar.org\/blog\/index.php\/wp-json\/wp\/v2\/posts\/420"}],"collection":[{"href":"https:\/\/rakkar.org\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rakkar.org\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rakkar.org\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rakkar.org\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=420"}],"version-history":[{"count":0,"href":"https:\/\/rakkar.org\/blog\/index.php\/wp-json\/wp\/v2\/posts\/420\/revisions"}],"wp:attachment":[{"href":"https:\/\/rakkar.org\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=420"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rakkar.org\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=420"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rakkar.org\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=420"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}