Re: slrn 0.9.9 to be released next weekend

On Saturday 09 August 2008 17:57:09 Sven Guckes wrote:

> * John E. Davis <[email protected]> [2008-08-09 18:54]:
> > Assuming no critical bugs are found in the latest version
> > (pre0.9.9-127), I intend to release 0.9.9 next Sunday (Aug 17).
> > It looks like the web pages and documentation are ready to go,

I'm aware of no documentation bugs, but I suggest synchronising with the 
slrn-doc repository before releasing. Please also let me know which version 
of the documentation you finally include, so that it can be made the basis of 
a "bugfix only" SVN branch. After 0.9.9, the slow process of abandoning 
Linuxdoc/SGML in favour of something better will begin in "trunk", so it 
won't surprise me if docs generated from "trunk" aren't usable for a while.

Please also encourage users to send documentation bugs to the slrn-doc bug 
tracker rather than bothering you with them: there's very little point in 
having a separate slrn-doc project if you have to forward every example of a 
typo to us. We now have our own bug tracker at 
<https://sourceforge.net/tracker/?group_id=4526>, and we'll be pleased if 
it's used. Posting to news.software.readers will also get the attention of 
the slrn-doc team.

> > and all that is needed is to change pre0.9.9-127 to 0.9.9.

I suggested "release candidate 1" before this message arrived. "0.9.9" is even 
better.

> alert the package maintainers!
>
> apropos:
> is there an up-to-date list
> of package maintainers?

<http://www.slrn.org/download.html#binaries>

Thomas W and Joerg S read this list. Other package maintainers can presumably 
be contacted after following the links. The only package that isn't up to 
date (in the sense of using the current stable version or higher) is the OS/2 
package, and if the maintainer is no longer interested I'm sure a replacement 
could be found in the small but enthusiastic OS/2 community on Usenet.

Another question: what about translators? Some of the slrn documentation is 
too huge to be easily updated by translators in eight days, but it would be 
nice if somebody hunted for untranslated/fuzzy strings in error messages and 
man pages, for instance. For anybody who wants to contribute translations, I 
can offer some basic technical support for using gettext, especially if 
you're willing to use the KBabel gettext front-end, as I do.

Meanwhile, let's hope there are no release-critical bugs!

-- 
PJR :-)

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/