[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-dev] release branching

From: Markus Gothe
Subject: Re: [Gnash-dev] release branching
Date: Thu, 21 Feb 2008 01:22:56 +0100

On 20 Feb 2008, at 17:40, Rob Savoye wrote:
I'm going to be making the release branch out of cvs HEAD shortly, most
likely in a few hours. While this isn't a call for everyone to throw in
last minute hacks, this is the time to make sure everything is clean to
be branched. Otherwise after I make the branch, we'll all be stuck
checking in code in both branches.

After the branch, the only checkins to it should be bug fixes, or
documentation updates. I discovered this week our docs are in seriously
sad shape, so I've been rewriting them. The initial changes are all
checked in as well, and at least now the chapters are in the correct
order. Much of the content is 2 years out of date.

I've got a bit of cleanup of how the documentation gets built that I'm
finishing up this morning. We now need both docbook-utils and docbook2X
to build the docs, and although they build fine for me, getting the
docbook tools working 100% correctly turns out to not be entirely
reproducible by everyone, which I'm trying to track down.

All I know by heart is LaTeX, unfortunately in this case(?)... I'll see IFF I get some spare time to learn docbook and that I'm alert enough to focus on a rewrite. OpenWRT is taking compiling time at (my other) work so I might be able to learn the fundamentals during compilation. Also afaik the Linux kernel docs are in docbook format, another excuse ;)


If anybody has ever felt like an in-the-closet tech-writer, and you know
docbook, this week is a good time for coming out of the closet. :-) I'll
be traveling for a week (FOSDEM, followed by an embedded systems
conference), and working on further manual rewriting. Ideally we'll do
the release itself as soon as I get back in town to my workstation with
a newly updated manual.

- rob -

Gnash-dev mailing list

Attachment: PGP.sig
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]