[Un, others] Places to announce your variant release

[andrewdoull]

Hi,

There's no where like in public to write your todo lists.

1. Upload files to Berlios.
2. Write Berlios news item.
3. Write angband.oook.cz forum announcement.
4. Write angband.oook.cz news item.
5. Update variant version release details on angband.oook.cz
6. Write rec.games.roguelike.angband post.
7. Write rec.games.roguelike.announce post.
8. Write blog article on unangband.blogspot.com.
9. Write blog article summary on roguelikedeveloper.blogspot.com.
10. Add news item to roguebasin.roguelikedevelopment.org.
11. Update version information on UnAngband entry on roguebasin.roguelikedevelopment.org.
12. After Linux and OS/X compiles uploaded, update freshmeat.net.

I also need to investigate writing a PAD file and using a automatic PAD file submitter to publicise it more widely.

All except 12 is done for 0.6.2-gold

Andrew

[Bandobras]

Wow. Show this to any clueless newbie that wants to start his own variant instead of contributing to one of the respectable, well-established variants we have around here.

You missed one, BTW: update entry in roguebasin variants list. Done for 0.6.2-gold.

[takkaria]

12. After Linux and OS/X compiles uploaded, update freshmeat.net.

Out of interest, how do the UnAngband Linux compiles get made and packaged?

[andrewdoull]

Wow. Show this to any clueless newbie that wants to start his own variant instead of contributing to one of the respectable, well-established variants we have around here.

It's depressing when you think that this is just to let people know that the release is out. And that's just the roguelike community, not random people.

You missed one, BTW: update entry in roguebasin variants list. Done for 0.6.2-gold.

Thanks.

[Bandobras]

Out of interest, how do the UnAngband Linux compiles get made and packaged?

Hand-crafted. Compiled using your Makefile.std. Then removed various random files that look unnecessary, like the whole src/ directory. Not ready for a multi-user system....

[takkaria]

Hand-crafted. Compiled using your Makefile.std. Then removed various random files that look unnecessary, like the whole src/ directory. Not ready for a multi-user system....

I might look into getting some linux build and packaging scripts set up for V, then. Also, would Un like an up-to-date autoconf solution along the lines of V?

[Bandobras]

I might look into getting some linux build and packaging scripts set up for V, then. Also, would Un like an up-to-date autoconf solution along the lines of V?

Sure. Your cross-Windows scripts helped me a lot whenever I wanted to release a Windows package compiled on Linux. About autoconf --- how much trouble is it to maintain it? The ancient makefiles work very well so far, though perhaps with SDL and GTK in the future they will require too much maintenance that autoconf provides for free...

[takkaria]

Sure. Your cross-Windows scripts helped me a lot whenever I wanted to release a Windows package compiled on Linux. About autoconf --- how much trouble is it to maintain it? The ancient makefiles work very well so far, though perhaps with SDL and GTK in the future they will require too much maintenance that autoconf provides for free...

The V autoconf requires just the same amount of work as Makefile.std -- they both use the same source file (Makefile.src). It's just that most casual Linux users like ./configure && make && make install.

Anyway, I'll put that on my todolist as recreational hacking. It's nice to have a break from V every now and again.