[xmlroff] ticket 30's milestone

[Tony Graham]

On Thu, Jul 12 2007 13:29:10 +0100, asmodai at in-nomine.org wrote:
> shouldn't ticket 30's milestone be adjusted? Right now it is still set to
> 0.5.0, I think you handled it for 0.5.1 though (which is missing from your
> milestones). :)

#30 is "Update libfo-examples for xmlroff 0.5.0".  It is not yet
complete.

0.5.1 is missing from the "Roadmap" [1] because it's marked as
completed.  You can see it if you click in the "Show already completed
milestones" box and then update.

#30 remains at 0.5.0 because it will be released as libfo-examples-0.5.0
when it's finally done (ideally next week).  libfo-examples is a few
variations based on what's in xmlroff.c that demonstrate different ways
to access libfo.

libfo-examples has to be updated for each xmlroff 0.x because the
filename of the libfo library follows the same numbering, so the current
version is libfo-0.5.a, etc.

Maybe it would be more sensible to change the libfo pkg-config .pc file
from libfo-0.5.pc to libfo.pc so it's then not strictly necessary to
update libfo-examples with each minor version increment, but that's
risky since the minor version increments when there's an incompatible
libfo interface change.

> And you are sure you want to deliver 0.5.2 in 3 weeks from now?

There's many definitions of the word "want".

My oft-stated intention is to make an xmlroff release "on or about" the
first of every month.  So you might not have noticed, but since xmlroff
0.5.0 was released in May, last Tuesday was 40th June (at least
according to the xmlroff calendar), which, for some definition of
"about", is about the first of June, which is when the release was due.

Leaving aside the calendar metaphysics, when I only made xmlroff
releases when things were relatively cooked, I used to find that people
concluded that xmlroff was inactive because of the long period since the
last release.  So I changed to the stated intention of releasing the
current code on or about the first of every month.  I don't always make
it (okay, I seldom make it), but it does induce me to make releases
rather than letting things slide too much.

What I want is to make regular, monthly releases that incorporate
improvements and bug fixes from other people as well as from me.

On a more pragmatic level, I want to make regular, monthly drops of the
current code.

On the level at which I was working when I set the milestone date, I
want to set the milestone to the first of the next month as the date at
which I'd like to do a release so I have a reminder to do the release in
a timely manner.

Regards,


Tony.

#30 http://xmlroff.org/ticket/30
[1] http://xmlroff.org/roadmap