From: Dave Kuhlman <dkuhlman@pa...> - 2008-06-10 21:50:44
> proceeding by the book (docs/dev/release.txt)
> * **On the Docutils-develop mailing list, announce that the release is
> going to be made, update the release notes and ask for additions.**
> this is the announcement
> the RELEASE-NOTES.txt is updated, please check for missings of important
> Next would be, depending on feedback.
> * **Announce a check-in freeze on Docutils-develop.**
> does this have to be enforced or is it quiet enough ?
I'd like to request that rst2odt.py/odtwriter be put in the queue for inclusion in the next release.
If there are things that I can do to get it ready for that, I'm willing to work on them.
One argument for including it is that rst2odt/odtwriter cannot be installed on top of an existing installation that was not installed from source. Docutils installs in an egg, and distutils does not handle installing on top of that.
By the way, I apologize for breaking the thread. My ISP does not respond the auto-confirm-response required by SourceForge. So, I have to post from another account.
From: David Goodger <goodger@py...> - 2008-06-13 13:43:29
On Tue, Jun 10, 2008 at 17:50, Dave Kuhlman <dkuhlman@...> wrote:
> I'd like to request that rst2odt.py/odtwriter be put in the queue for inclusion in the next release.
> If there are things that I can do to get it ready for that, I'm willing to work on them.
Engelbert Gruber asked me off-list if I had any objection, and this is
what I answered:
"I haven't tried it. At a minimum, it needs documentation and tests,
and it should be able to process docutils/docs/user/rst/demo.txt
without crashing. If it can do all those things, I have no
To clarify the demo.txt part, I mean the "reasonably complete"
criterion from http://docutils.sourceforge.net/docs/dev/policies.html#check-ins:
Reasonably complete means that the code must handle all input.
Here "handle" means that no input can cause the code to fail (cause
an exception, or silently and incorrectly produce nothing).
"Reasonably complete" does not mean "finished" (no work left to be
done). For example, a writer must handle every standard element
from the Docutils document model; for unimplemented elements, it
must *at the very least* warn that "Output for element X is not yet
implemented in writer Y".
I recommend reading the rest of that doc as well. I'm sorry that I
don't have time to help out more right now; I have too much going on,
too many obligations.
David Goodger <http://python.net/~goodger>