Hi devs,
since we're now using DocBook as source format for all our
documentation, it would technically be relatively easy to publish things
like the MAN page or the UserGuide in EPUB format as well.
The latest versions of pandoc ( 1.12.x) offer a DocBook reader and do
a, more or less, good
Now we have default and python3-port as working branches, we need a
workflow that ensures they are kept in sync. If python3-port is left
behind, then all the work to date will have been for nought.
I also need advice on how to handle feature clones: I have the
SCons_D_Tooling clone and have no
Hi Russel,
On 04.10.2013 19:23, Russel Winder wrote:
Now we have default and python3-port as working branches, we need a
workflow that ensures they are kept in sync. If python3-port is left
behind, then all the work to date will have been for nought.
hmmm, we probably should discuss (and then
On Fri, Oct 4, 2013 at 2:10 PM, Dirk Bächle tshor...@gmx.de wrote:
Hi Russel,
On 04.10.2013 19:23, Russel Winder wrote:
Now we have default and python3-port as working branches, we need a
workflow that ensures they are kept in sync. If python3-port is left
behind, then all the work to
On Fri, 2013-10-04 at 20:10 +0200, Dirk Bächle wrote:
[…]
hmmm, we probably should discuss (and then decide) how we want
development to look like, once we have a working python3 branch. Will we
continue to support both major versions 2.x and 3.x? If yes, in which
direction (2-3 or 3-2) do
I like the idea since I like ebooks. However, I will be honest and say
that for code development I would not be too likely to use it since on my
desktop machines I don't have a great epub viewers.
So I guess I would say that if there was no extra effort or file space
required go ahead and add it
