Hi,
Currently we are building against the 1.4 branch of jackrabbit. Some
concerns were raised that we could be diverting to far from the current
trunk and thus be missing out on fixes and making upgrading very hard.
I just want to know how people are thinking about upgrading to trunk and
how we should do that. Some questions I would have are:
- Would we maintain two branches of the repository: one on 1.4 and one
on trunk?
- How stable is the jackrabbit trunk (as in crashes while running)?
- How stable is the jackrabbit trunk code (as in api changes, major code
refactoring)?
- How much effort would it take now to upgrade to the trunk?
- How much effort would it take to upgrade to the 1.5 when it's released?
- How much effort would it take to upgrade between trunk snapshots?
- Could we get 'stuck' to our own build snapshot of jr because we can
not or don't want to upgrade to the latest version of the trunk?
I do see the need to stay "in touch" with the jackrabbit trunk, but I
also do have some concerns about upgrading to the trunk.
So WDYT?
I don't want to create sides, so please refrain from just "+1, yes
upgrade!" or "-1, going to trunk is evil" statements and let's try to
find out what to pro's and con's of upgrading are and how an upgrade
would eventually fit in our release cycles.
Regards,
Bart
--
Hippo B.V. - Amsterdam
Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466
Hippo USA Inc. - San Francisco
101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646
-----------------------------------------------------------------
http://www.onehippo.com - [EMAIL PROTECTED]
-----------------------------------------------------------------
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
