Lenya 1.3

Starting a new thread because this response did not belong
in the
current thread about 2.0/2.1.

On 2/7/08, Jann Forrer <jann.forrerid.uzh.ch> wrote:
> Jörn Nettingsmeier wrote:
>  > solproviderapache.org wrote:
>  >> On 2/7/08, Jann Forrer <jann.forrerid.uzh.ch> wrote:
>  >>> I think we should try to avoid breaking
backwards compatibility or if we
>  >>>  really have to, a migration path should
be described.
>  >>>  What should we propose to people still
using 1.2. Upgrading to 2.0 or
>  >>>  wait for 2.1? If 2.1 is not backward
compatible with 2.0 we will have
>  >>>  three version which are not compatible
which makes upgrading a real pain
>  >>>  :-(
>  >>>  Jann
>  >> Let Lenya 1.2 users upgrade to Lenya 1.3
since complete
>  >> backwards-compatibility was a goal. Lenya 1.3
should be usable in a
>  >> few weeks.  The high-level feature list reads
just like 2.0's What's
>  >> New.  The largest strategic difference is no
Java in Modules, but that
>  >> cannot be a problem since 1.2 did not have
that feature.  Just copy
>  >> Lenya 1.2 Publications to the pubs directory.
 The implementations is
>  >> very different from Lenya 2, but a normal
user will not care.  The new
>  >> features become available after a simple
conversion to the new
>  >> datastore.  (Jorn will love that Areas have
been removed.)
>  >>
>  >> This frees Lenya 2 development to focus on
new features for new installations.
>  >
>  > now that your work on 1.3 has gained momentum, we
should really discuss
>  > what to do with it to take the best of both
worlds into lenya 3.0... the
>  > current situation is somewhat unfortunate - i'm
sure there are many good
>  > ideas in 1.3, but i have no time to track it, and
i guess the same is
>  > true for the other 2.0 devs.
>  > it would be really great if you gave a 1.3
presentation at a lenya
>  > hackathon one of these days - got any vacation
plans to old europe?
>
> That would be nice 
>  I like the idea of the 1.3 backward compatiblity but
changing from 1.2
>  to 1.3 is risky because solprovider is the only dev
working on this
>  version. And if you want to move from 1.3 to 2.x you
will probably have
>  the same problems as changing from 1.2. to 2.x.
>
>  Jann

As Thorsten mentioned, 1.3 is still unofficial.  I am not
suggesting
that the status should change today.  While all 1.2
functionality
still works, wait until 1.3 is feature complete with 1.2
before we
discuss what to do with it.  I should finish "Add new
Resource" soon.
Security is the last needed feature; that should be
completed in a few
weeks at my current pace.  Clean up, testing, and much of
the new
functionality are happening when I need a break from the
major tasks.

Once 1.3 does everything that 1.2 does, we should merge any
patches
from the 1.2.x branch.  I started with 1.2.5 so there should
be a few
patches.  Most patches probably only affect unconverted 1.2
Publications, but the merge is necessary to be
"completely
backwards-compatible." I would like Lenya 1.3 to
replace the 1.2.x
branch.

I know as much about 2.0 as everybody else knows about 1.3. 
1.3 is
basically 1.2 simplified.  I have no plans to visit Europe
(but that
can change.)  Documentation is already in the Lenya 1.3
directory; I
will prepare a briefing specifically for Lenya devs, and we
can
schedule something.

If I understand correctly, 2.x uses a flat datastore. 
Installing 1.3,
converting to 1.3's flat datastore, then upgrading to 2.x
may be
simpler than a direct 1.2->2.x conversion.  We could also
discuss
using 1.3's datastore in 2.x; 1.3 replaces Areas with
versioning and
may have a good interface for adding JCR and other
repositories.

Upgrading functions may be more difficult, but 1.3's Modules
and 2.0's
Modules should be able to coexist.  Save that for later when
at least
one person understands both systems.

Thanks for reading my ramblings,
solprovider

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribelenya.apache.org
For additional commands, e-mail: dev-helplenya.apache.org