On 14/02/2015 14:26, Guido Wimmel wrote:
On 13.02.2015 17:09, Francesco Chicchiriccò wrote:
On 13/02/2015 16:59, andrea patricelli wrote:
Il 13/02/2015 12:49, Francesco Chicchiriccò ha scritto:
Hi all,
after some time, following our former discussion [1], I've been
able to complete the planned refactoring (see SYNCOPE-620).
Please take a look and let me know what you think - in the 2_0_X
branch.
If you agree, I would also propose to replace the current master
branch (with version set to 1.3.0-SNAPSHOT) with 2_0_X branch, and
consequently move all issues planned for 1.3.0 to 2.0.0 in JIRA.
The rationale is that all improvements for 1.3.0 were migrated as
well, and I don't actually see likely any 1.3 release to occur
anytime soon.
WDYT?
+1
Great work, definitely +1.
Is it feasible and useful to think about an upgrader from version 1
to 2 as pointed out in the discussion?
Given the relevant differences (package name changes, module
re-organization, file renamed or created) between 1.2.X and 2.0.X,
IMO the simpler and most effective solution would be to detail an
upgrade procedure starting with the generation of a new 2.0.0 project.
An upgrader module - as delivered with 1.1.0 and 1.2.0 has proven to
be pointless to maintain, so I am quite dubious about it...
Which upgrader module do you mean? The ContentUpgrader and upgrade
scripts for Syncope 1.1 -> 1.2 made changes
to content in an existing 1.2-based database - this would be necessary
for 1.2 -> 2.0 as well if data structures change, right?
To upgrade a project (war overlay with code/modified Spring configs)
it would be nice to have at least a short
description in the Wiki of the changes
(maybe in form of a table that compares the modules / packages of 1.2
with 2.0). Probably a large part of a migration
would be to consistently replace imports etc... - right?
Such a description would also help people to incorporate commits to
1.2.X into 2.0.X, as this probably needs to be done
manually (not via merging)?
Hi Guido,
this is definitely a nice suggestion: before merging 2_0_X into master
and resolving SYNCOPE-620 I am going to draft a wiki page under the
terms you write above.
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
