https://www.chiliproject.org/2010-12-29T10:57:25+01:00ChiliProjectChiliProject - Task #32: Create an upgrade path from Redmine https://www.chiliproject.org/issues/32?journal_id=97342010-12-29T10:57:25+01:00Muntek Singhsikhnerd@gmail.com
<ul><li><strong>Start date</strong> set to <i>2010-12-29</i></li><li><strong>Estimated time</strong> deleted ()</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Normal</i></li><li><strong>Project</strong> set to <i>ChiliProject</i></li><li><strong>Target version</strong> deleted ()</li><li><strong>Assignee</strong> deleted ()</li><li><strong>% Done</strong> changed from <i>0</i> to <i>0</i></li><li><strong>Subject</strong> set to <i>Create an upgrade path from Redmine </i></li><li><strong>Category</strong> deleted ()</li><li><strong>Tracker</strong> set to <i>Task</i></li><li><strong>Due date</strong> deleted ()</li><li><strong>Subproject of</strong> deleted ()</li><li><strong>Description</strong> set to <i>Create an upgrade path from Redmine
</i> <a href="/journals/9734/diff/description" class="lightbox-ajax">More</a></li><li><strong>Status</strong> changed from <i>Open</i> to <i>Open</i></li></ul> ChiliProject - Task #32: Create an upgrade path from Redmine https://www.chiliproject.org/issues/32?journal_id=622010-12-29T16:55:36+01:00Eric Davis
<ul><li><strong>Target version</strong> deleted ()</li></ul><p>Will need to address this soon after going public.</p> ChiliProject - Task #32: Create an upgrade path from Redmine https://www.chiliproject.org/issues/32?journal_id=752010-12-30T09:17:20+01:00Muntek Singhsikhnerd@gmail.com
<ul></ul><p>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.</p>
<p>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.</p>
<p>Also, how is this affected by <a href="https://www.chiliproject.org/issues/31" class="issue status-1 priority-2" title="Create a compatibility process showing how to share code with Redmine (Open)">#31</a> ?</p> ChiliProject - Task #32: Create an upgrade path from Redmine https://www.chiliproject.org/issues/32?journal_id=2832011-01-12T14:29:29+01:00Eric Davis
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Task</i></li></ul> ChiliProject - Task #32: Create an upgrade path from Redmine https://www.chiliproject.org/issues/32?journal_id=3272011-01-13T15:36:11+01:00Eric Davis
<ul><li><strong>Subproject of</strong> deleted (<strike><i>#28</i></strike>)</li></ul> ChiliProject - Task #32: Create an upgrade path from Redmine https://www.chiliproject.org/issues/32?journal_id=7002011-02-01T22:49:41+01:00Felix Schäferfelix+chili@oh14.de
<ul><li><strong>Status</strong> set to <i>Open</i></li></ul>