ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Create an upgrade path from Redmine (Task #32)

Added by Muntek Singh at 2010-12-29 10:57 am. Updated at 2011-02-01 10:49 pm.

Status:Open Start date:2010-12-29
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Remote issue URL:

Description

Create an upgrade path from Redmine

Related issues

related to Task #28: Code Fork Declined

History

#1
Updated by Eric Davis at 2010-12-29 04:55 pm

Will need to address this soon after going public.

  • Target version deleted ()

#2
Updated by Muntek Singh at 2010-12-30 09:17 am

I think Joomla's route of maintaining compatibility with the parent for the first few releases, but have a clear roadmap and version where compatibility breaks and we no longer care about the parent is the best route to go. This gives plugin authors time to update plugins to "our" changes and give a clear timeline of when we stop expending extra effort to main compatibility.

To me this means we should create and maintain an import script redmine->bluemine from the first release, then the day we break compatibility, the import script is a one-way one-time affair. I'm not familiar enough with the code changes planned and already happening to know how viable this is, but I think there should be a certain point where we prioritize adding our own cool features and fixes over maintaining strict compatibility.

Also, how is this affected by #31 ?

#3
Updated by Eric Davis at 2011-01-12 02:29 pm

  • Tracker changed from Bug to Task

#4
Updated by Eric Davis at 2011-01-13 03:36 pm

  • Subproject of deleted (#28)

#5
Updated by Felix Schäfer at 2011-02-01 10:49 pm

  • Status set to Open

Also available in: Atom PDF