On 11/12/2014 08:22, Guido Wimmel wrote:
Hi Francesco,
On 09.12.2014 17:37, Francesco Chicchiriccò wrote:
Hi all,
I think it is time to re-organize our codebase in order to allow
easier maintenance and simplify extendability.
I have put a proposal at [1] - as you can see it is an empty skeleton
with README.md on each directory explaining the purpose of the
related module.
My idea is to start this (huge) refactoring for Apache Syncope 2.0,
e.g. on a new branch.
WDYT?
I see it with mixed feelings...
Actually the new code organization looks good, and it is a good thing
to refactor the growing codebase for
better maintainability and extendability.
On the other hand, I'd expect considerable upgrade effort/risk for
projects (like ours) based on the current archetype and including
custom modifications.
Do you think one could provide an appropriate upgrade path for such
projects?
Hi Guido,
I was actually expecting similar concerns from your side :-)
As you've recently seen with 1.2, we always provide an upgrade procedure
(with supporting module, if needed), and I think we should keep this way
also for 2.0.
Naturally, there are some limitations, the procedure can't be
bullet-proof for each and every scenario, but it has to be good enough
for easing the upgrade process with reasonable effort.
Regards.
[1] https://github.com/ilgrosso/syncope2
--
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/
