'Re: [Gnash-dev] release branching'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnash-dev
Subject:    Re: [Gnash-dev] release branching
From:       Markus Gothe <nietzsche () lysator ! liu ! se>
Date:       2008-02-21 0:22:56
Message-ID: 10D44E13-4D97-4677-A7AD-B9293F72C26D () lysator ! liu ! se
[Download RAW message or body]

[Attachment #2 (multipart/signed)]

[Attachment #4 (multipart/alternative)]

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 ;)

//Markus

> 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
> Gnash-dev@gnu.org
> http://lists.gnu.org/mailman/listinfo/gnash-dev

[Attachment #7 (text/html)]

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; \
-webkit-line-break: after-white-space; "><br><div><html>On 20 Feb 2008, at 17:40, Rob \
Savoye wrote:</html><br class="Apple-interchange-newline"><blockquote type="cite">I'm \
going to be making the release branch out of cvs HEAD shortly, most<br>likely in a \
few hours. While this isn't a call for everyone to throw in<br>last minute hacks, \
this is the time to make sure everything is clean to<br>be branched. Otherwise after \
I make the branch, we'll all be stuck<br>checking in code in both \
branches.<br><br>After the branch, the only checkins to it should be bug fixes, \
or<br>documentation updates. I discovered this week our docs are in seriously<br>sad \
shape, so I've been rewriting them. The initial changes are all<br>checked in as \
well, and at least now the chapters are in the correct<br>order. Much of the content \
is 2 years out of date.<br><br>I've got a bit of cleanup of how the documentation \
gets built that I'm<br>finishing up this morning. We now need both docbook-utils and \
docbook2X<br>to build the docs, and although they build fine for me, getting \
the<br>docbook tools working 100% correctly turns out to not be \
entirely<br>reproducible by everyone, which I'm trying to track \
down.<br><br></blockquote><div><br></div>All I know by heart is \
LaTeX,&nbsp;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 \
;)</div><div><br></div><div>//Markus</div><div><br><blockquote type="cite">If anybody \
has ever felt like an in-the-closet tech-writer, and you know<br>docbook, this week \
is a good time for coming out of the closet. :-) I'll<br>be traveling for a week \
(FOSDEM, followed by an embedded systems<br>conference), and working on further \
manual rewriting. Ideally we'll do<br>the release itself as soon as I get back in \
town to my workstation with<br>a newly updated manual.<br><br><span \
class="Apple-tab-span" style="white-space:pre">	</span>- rob \
-<br><br><br>_______________________________________________<br>Gnash-dev mailing \
list<br><a href="mailto:Gnash-dev@gnu.org">Gnash-dev@gnu.org</a><br><a \
href="http://lists.gnu.org/mailman/listinfo/gnash-dev">http://lists.gnu.org/mailman/listinfo/gnash-dev</a><br></blockquote></div><br></body></html>

["PGP.sig" (application/pgp-signature)]

_______________________________________________
Gnash-dev mailing list
Gnash-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnash-dev

[prev in list] [next in list] [prev in thread] [next in thread] 