This is what I sent to T3 the first time he did it. As you have merge access, you all you would need to do is download the zip file from the github.
I update the version number and add Jay, submit the pull request to me. Once you've done that, I'll merge it. Once I've merged it, download the ZIP file from github for the master branch. This will give you a clean install of PRISM that you can release.
I look at the commit history between 0.4.4's release and the release that I'm putting out. From there I just use the commit information that I find interesting, or important. Like adding the name for a timer is a BC break, and must be mentioned in the change log.
You have to do two things at once. This is the process that I go through. Reply to PHPInSimMod - PRISM Releases. In the reply to that thread title the reply "PHPInSimMod (PRISM) 0.4.5". Then you have to include the change log from version 0.4.4 to 0.4.5. Attach the ZIP file to this thread, that contains clean installation of PRISM 0.4.5. That means no config files, except for the examples. Don't hit the reply button yet.
Then once you've done that, open a new tab in your browser and make a new thread in PHPInSimMod - PRISM Sub-Forum. In this your going to write
And then attach the change log list that you put into the other thread. Once you've done this, go back to the Releases reply and hit submit and copy the URL and make the "PHPInSimMod - PRISM 0.4.5" text a link to that thread. Hit submit.
Sticky 0.4.5's thread, and un-sticky 0.4.4's thread.
Should I do 0.5.0.8 or should I increase to 0.5.1? Wasn't sure since it's not a major update, but it's also not a hotfix. I think we should start another thread to discuss the version numbering schema, and what we want to do future releases as.
But I suppose we need to discuss where we want to go from here on forward.
Edit: I know on my personal projects I usually do year.month.day.TimeinGMT24hrFormat such as 16.04.07.2230. but I don't think that would be the optimal version number schema for PRISM.