[Doc-SIG] Plans for Docutils
David Goodger
goodger at python.org
Tue Mar 30 22:29:01 EST 2004
I have had some queries recently about current plans for
Docutils. There's some pressure for a new release soon.
I'd like to do a release, but there are outstanding issues.
Here's a summary:
* Many improvements were made during the Docutils sprint at
PyCon. I'm just beginning to work my way through them.
There may be some issues to be resolved; don't know yet.
In any case, I have to go through all the checkins before
I'll be comfortable with an official release, for my own
peace of mind and so I understand what's what.
I hope to write & post a summary of what was accomplished
at the sprints, soon.
* My mail wasn't flowing for a while, but it's back now.
If anybody got a bounce (or lack of reply), please
re-send.
* The nested inline markup patch is still outstanding.
Unfortunately, although Steve Holden was threatening to
attack it, pressing duties (organizing PyCon itself) got
in the way.
David Abrahams (the author of the patch, on the "nesting"
branch in CVS) is understandably anxious for a code review.
I'd love for this to go live soon, and it'd be a shame if
it wasn't in the next release. I will try.
* Recently I wrote that Docutils could use a release manager,
and called for volunteers. Paul Moore wrote:
What's needed beyond taking the latest snapshot and
calling it 0.4?
I replied, but the reply didn't seem to make it to the list,
so here it is again:
Making sure there aren't any bugs due to recent checkins,
for one. ;-) There's a procedure at
<http://docutils.sf.net/spec/notes.html#release-procedure>,
which should be fleshed out as required.
A useful function of a real release manager would be to push &
prod me and other developers to polish the codebase where it
seems to be deficient. Also, establish a cutoff date and put a
moratorium on new features. Stuff like that. We're a much
smaller project than Python, but perhaps we could learn from
their procedures (if they've got any ;-).
* The "blurbs"/"plain lists"/"line blocks" feature is in limbo
and ought to be resolved. There may be other features in the
same state.
In the meantime, if you're interested, here's my account
of PyCon DC 2004: <http://python.net/~goodger/pycon_dc_2004/>.
Many thanks to all the participants. I will be contacting each
of you individually soon.
--
David Goodger http://python.net/~goodger
For hire: http://python.net/~goodger/cv
More information about the Doc-SIG
mailing list