On 18.01.2007, at 15:18, Sameer Charles wrote:
> Sure, it depends on the release plan. We can always move features
> or fixes which needs much more changes to future versions.
>
>> That is why we bring the new jackrabbit version in 3.1 and not in
>> 3.0 branch. Anyway we need to think about to facilitate migration.
>> Perhaps dropping a migrate module jar into the 3.0 instance will
>> do the job. This module could provide a migrate tool where you
>> select what content you like to migrate and thats it.
>
> I am not sure, I think it would be the best if we delegate upgrade/
> migration to core + modules instead of separate tool like what we
> have now.
> we need to make sure that basic repository can be migrated without
> any effort from the users who are upgrading, in addition all
> modules / module vendors should take care of auto migration (any
> config changes etc..).
>
I had more the case in mind, where you can't omit migration through
activation (like incompatible jackrabbit version), but in general the
update by dropping new core/module jars is much the better choice.
They will do the incremental update on the current instance.
Philipp
>
> Cheers
> - Sameer
>
>
>
> On Jan 18, 2007, at 2:29 PM, Philipp Bracher wrote:
>
>>> There are other feature set which must be implemented for 3.1
>>
>> If we plan a 3.2 with the more complex extensions, we could
>> release a 3.1 soon. I'm afraid that the release of 3.1 will take
>> again for ever if we put to much into it and do major architecture
>> changes like activation. In my opinion we should stick to the
>> architecture we have in 3.0 for the 3.1 release but improve the
>> product by doing the easy todos bringing the biggest benefit.
>>
>>> from my side
>>> - Transactional activation (high priority)
>>> - compatibility with webSphere (blocker)
>>> - WebDAV
>>>
>>> So I dont think it will be that soon.
>>> I wasn't able to move to even Jackrabbit 1.1 without breaking
>>> existing versions, we have to think for the people who are
>>> already using magnolia 3.0.x in production.
>>
>> That is why we bring the new jackrabbit version in 3.1 and not in
>> 3.0 branch. Anyway we need to think about to facilitate migration.
>> Perhaps dropping a migrate module jar into the 3.0 instance will
>> do the job. This module could provide a migrate tool where you
>> select what content you like to migrate and thats it.
>>
>> The discussion has started ;-)
>>
>> Philipp Bracher
>>
>>
>>>
>>> Cheers
>>> - Sameer
>>>
>>> On Jan 18, 2007, at 2:00 PM, Philipp Bracher wrote:
>>>
>>>>
>>>> On 18.01.2007, at 12:54, Fabrizio Giustina wrote:
>>>>
>>>>> On 1/18/07, Philipp Bracher <[email protected]> wrote:
>>>>>> I have created the 3.0 branch in svn. The trunk is now the new
>>>>>> 3.1
>>>>>> version (poms need to be updated). Our plan is to keep the 3.0
>>>>>> branch
>>>>>> as stable as possible (only bugfixes with small impact).
>>>>>
>>>>> nice, so can we try upgrading to new deps on trunk? (jackrabbit
>>>>> 1.2 is
>>>>> on the way, and it will also brings in lucene 2). If no
other big
>>>>> changes are coming at the moment it would be great to release a
>>>>> 3.1
>>>>> version with these updated dependencies soon.
>>>>
>>>> Yes we can update the trunk in my opinion. If this works fine
>>>> this could really be a reason for releasing 3.1 with some other
>>>> smaller new features and bugfixes.
>>>>
>>>> We will try to define the feature set of 3.1 next week. some
>>>> first ideas:
>>>> - links to other repositories (fck editor support)
>>>> - advanced search (nearly ready as a separate module)
>>>> - usability (keep selected path ,...
>>>> - better main bar (direct activation, flexible functions adding)
>>>>
>>>> Philipp Bracher
>>>>
>>>> ----------------------------------------------------------------
>>>> for list details see
>>>> http://www.magnolia.info/en/magnolia/developer.html
>>>> ----------------------------------------------------------------
>>>
>>> Regards,
>>>
>>> Sameer Charles
>>> Magnolia International Ltd.
>>>
>>>
--------------------------------------------------------------------
>>> -------------
>>> [EMAIL PROTECTED] http://www.magnolia.info
>>> Magnolia(r) - Simple Enterprise Content Management
>>>
--------------------------------------------------------------------
>>> -------------
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ----------------------------------------------------------------
>>> for list details see
>>> http://www.magnolia.info/en/magnolia/developer.html
>>> ----------------------------------------------------------------
>>
>>
>> ----------------------------------------------------------------
>> for list details see
>> http://www.magnolia.info/en/magnolia/developer.html
>> ----------------------------------------------------------------
>
> Regards,
>
> Sameer Charles
> Magnolia International Ltd.
>
>
---------------------------------------------------------------------
-
> -----------
> [EMAIL PROTECTED] http://www.magnolia.info
> Magnolia(r) - Simple Enterprise Content Management
>
---------------------------------------------------------------------
-
> -----------
>
>
>
>
>
>
>
> ----------------------------------------------------------------
> for list details see
> http://www.magnolia.info/en/magnolia/developer.html
> ----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
