groff
[Top][All Lists]
Advanced

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

Re: [Groff] Trying to understand groff development and release model


From: Halim Issa
Subject: Re: [Groff] Trying to understand groff development and release model
Date: Mon, 15 Dec 2008 17:46:48 +0100
User-agent: KMail/1.10.3 (Linux/2.6.27.7; KDE/4.1.3; i686; ; )

Hi Werner,

On Monday 15 December 2008 14:13:53 Werner LEMBERG wrote:
> It should be released as soon as possible, I fully agree.
> Unfortunately, it's only me who is working on groff, and I can't
> afford enough time to really come to the point where I can
> wholeheartily say `it's time to do a release'...

First of all - thanks much for taking the time to answer on top of a full 
schedule. I fully sympathise with your challenge of being sole maintainer of 
the project. 

> Well, I should probably release the current CVS as 1.19.3, regardless
> of its state...

I am not sufficiently skilled in reading and judging patches in cvs to qualify 
which patches are in such a state to be release-worthy or not. Unfortunately. 

But my gut feeling tells me that if current cvs a) is used by yourself and a 
few others on a (semi-)daily basis without problems, and b) you have been at 
least somewhat restrictive against letting sloppy patches in, maybe releasing 
current cvs as 1.19.3 BETA-1 would increase a sufficient amount of interest to 
have any showstopper bugs identified so that you can perhaps release a final 
1.19.3 over the Holidays?

If there's anything I can do to assist in any way from a non-C-coder point of 
view, please let me know - I'd really like to see more utf-8 capabilities in 
groff so that we can move closer to a fully utf-8-capable console during 2009.

Thanks again for your quick reply, your openness around the challenges, and 
your willingness to explore releasing CVS as 1.19.3(beta) !

 -h




reply via email to

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