[daisy] Daisy release planning

[Bruno Dumon]

On Wed, 2007-03-07 at 11:07 +0100, Andreas Deininger wrote:
> 2007/3/6, Bruno Dumon <bruno at outerthought.org>:
> > Hi,
> >
> > It's time we get Daisy 2.0 released, so we'll stop adding new stuff and
> > polish the current subversion trunk.
> >
> > This is what we have in mind:
> >
> > * March 16: Daisy 2.0 beta release
> >
> > * March 30: Daisy 2.0 final release
> >
> > So this is also a call to report any remaining issues (bugs, design
> > problems, documentation errors, whatever) with Daisy 2.0.
> 
> There are a few issues I would like to address:
> 
> * nice if my patch for DSY-367 could be applied, though it is only a
> minor change

I'll have a look at it.

> * regarding DSY-405: can that make the way into the 2.0 release?
> I acknowledge that inside my patch, invoking the wrapper scripts is
> not implemented satisfactorily yet, since the path names are hardcoded
> inside the wrapper scripts in the installation directory, so that they
> will get lost during an update
>  I see two possibilities in order to resolve that:
> 
> - not hardcoding any path in the script at all, everything is done via
> environment variables
> - creating two 'bin' directories inside the daisywiki datadir and the
> daisy datadir, both containing a small script (with hardcoded path
> name(s)) that invoke the according wrapper script inside the daisy
> installation directory.
> 
> Personally I would tend to the second option since the first solution
> does not work well with multiple daisy instances on a single machine
> and also means that manual intervention by setting of the environment
> variables is needed

If you can provide an updated patch, I'll apply it.

> * I really appreciate that the styling of the repository installation
> is improved, in the course of that action (or separately) the
> following issue should be addressed also (IMHO):
> http://lists.cocoondev.org/pipermail/daisy/2007-February/005892.html
> 

I actually started looking at this, but I found the current scripts
rather complex to comprehend, especially with the duplicate paths for
interactive and automated operation. I don't think I can spend time
working on this right now (writing an upgrade script would then probably
be higher priority, but we're not planning on doing that either).

> * I18N?

(done)

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno at outerthought.org                          bruno at apache.org