Release protocol

[VictorGijsbers]

PREPARATION

• Make a list of most important changes.
• Write an release announcement incorporating this list.
• Update the list of extensions
• Update list of CC licenced images etc
• Put all images through the compressor (https://github.com/i7/kerkerkruip/issues/41#issuecomment-13217381)

FINAL BUILD (@curiousdannii)

• Put correct version in game title
• Generation info must be set to false.
• Glimmr must be commented in and Extended Debugging commented out.
• Build a release version.

POST-BUILD (@curiousdannii)

• Rename the file to Kerkerkruip.gblorb. (Otherwise the .ini won't work.)
• Final test whether it runs in gargoyle.

PACKAGING (@curiousdannii)

• Put game file and ini file in a zip archive.
• Create OS specific installers
• If it's a major release then create a release branch now (so that the installers are included)

RELEASE

• Upload the file to lilith.cc.
• Update the lilith.cc Kerkerkruip page.
• Upload new version to IF Archive.

ANNOUNCEMENTS

• Announce at Kerkerkruip.org
• Announce at Gaming Philosopher.
• Announce at IFDB.
• Announce at intfiction.org.
• Announce at Temple of the Roguelike forum.
• Update page at roguebasin, and add to new releases.
• Announce at audiogames.net.
• If the Bay12 topic remains alive: announce it in there.
• Add release notes to IFWiki.
• Update Kerkerkruip wiki?

[curiousdannii]

We need a basic release as well, for Quixe, and for audio users. If neither Glimmr nor Flexible Windows are included will it just use a normal two window interface?

The Windows and Debian packages are almost complete, though I suggest we wait for the OSX and website before we release them formally.

[ektemple]

The Glimmr Additions extension is designed to be detachable, but the Windows extension should work fine w/Quixe. No need to leave it out (it's not detachable anyway).

On Tue, May 7, 2013 at 6:16 PM, Dannii Willis notifications@github.comwrote:

We need a basic release as well, for Quixe, and for audio users. If neither Glimmr nor Flexible Windows are included will it just use a normal two window interface?

The Windows and Debian packages are almost complete, though I suggest we wait for the OSX and website before we release them formally.

— Reply to this email directly or view it on GitHubhttps://github.com/i7/kerkerkruip/issues/70#issuecomment-17576765 .

[curiousdannii]

Should it be released as a zip now that we're providing an ini file?

[VictorGijsbers]

Yes, I guess it should be released as a zip. (Though I'll continue putting a gblorb at the "latest-release.gblorb" URL, for now at least.)

[ektemple]

Since it's not explicitly mentioned above, let me note that Extended Debugging needs to be commented out from story.ni on release (this extension is needed to release test builds on a Mac, due to a serious bug in the IDE.)

[VictorGijsbers]

So, on a scale of 1 to 10, how bad is it that I did NOT comment out Extended Debugging for release 8 / 8,1?

[ektemple]

It's kind of bad--folks will be able to PURLOIN, see the FULL MAP, and do lots of other stuff they oughtn't to...

Sorry for not thinking of adding it to the protocol before release...

[VictorGijsbers]

Well, that's kind of bad. Kerkerkruip 8 is the version with cheat codes, then. ;)

[VictorGijsbers]

I have released and uploaded a new version 8.2. I announced this at the int-fiction forum, but not yet at the other fora; the response there is lower, and I don't really want to spam people. If you think I should announce it more broadly, let me know. (Anyone following the normal download link will of course get the new version automatically.)

[curiousdannii]

Github now has a more substantial release system, which looks like it would be good to use. https://github.com/blog/1547-release-your-software

From the screenshots it looks like it might track downloads too, which is why I'm suggesting it. Actually I don't think it does :(

[VictorGijsbers]

Hm; might not be too useful then?

[curiousdannii]

We could still use git tags to pin point the exact source code of each release. I think that would be valuable.

[VictorGijsbers]

What are git tags?

[curiousdannii]

Permanent labels which point to specific commits. They're usually used for marking each version. The Github releases system allows you to then add a description (release notes etc) for each tag, as well as other files such as installers.

[curiousdannii]

Because I'm the one doing the installers, I'd like to suggest that I do the official final build too. I can then put them in my dropbox for Victor to take over for the release and announcement stages. What do you think?

[VictorGijsbers]

That sounds great, Dannii. Let's make the last few adjustments needed, perhaps play the game a bit over the next couple of days, and get this done somewhere within the next 8 days. Would that be possible?

[curiousdannii]

Yep that sounds good.

I opened up my ubuntu virtualbox for the first time in many months and had hundreds of updates to install!

[VictorGijsbers]

Dannii, can you build the files? I'll get back to you about the hosting tomorrow, but I don't think it's super necessary to sort all that out (as long as we keep the same domain). Or do we think it's important to have the new wiki up and running before we release?

[mciul]

I think releasing sooner would be better.

[curiousdannii]

I've moved this to a wiki page (which we can all still edit).

I'll make a roadmap to version 10 issue, which can be the one place for discussing stuff like this, rather than splitting it up into two issues like we did this time.