Databases
StackOverflow2013
Postsdbo
PORecommendations for migrating custom code mods to new major release of open source software?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORecommendations for migrating custom code mods to new major release of open source software?
    primarykey
    data
    text
    <p>I've got a (dirty) production installation of Simple Machines Forum (SMF 1.1.13). It was a clean install, once... about five years, twenty updates, and 40 mods ago. Not to mention the custom code that was patched directly into the code base. This started as a for-fun side project, and didn't have any code management practices at the get-go.</p> <p>Now SMF 2 is (getting closer to) going live, and I want to upgrade. But without leaving the custom features behind.</p> <p><strong>Keep reading, this is a general software management question, not an SMF support question...</strong></p> <p>I'm trying to figure out the best way to port the custom features into the new code branch.</p> <ul> <li>In some cases, the custom 1.1.x functionality will already exist in 2.0. Yay, no work for me!</li> <li>In some cases, there will be mod packages versioned for 2.0, and I can just install them directly on a clean SMF 2 build. Yay, minimal work for me!</li> <li>In some cases, the code port will be fairly straightforward between the two versions (e.g. a few small changes in queries or global variable construction). (I've ported a few features/mods <em>back</em> from 2.0 to 1.1.x, so I'm starting to get familiar with it.)</li> <li>In some cases, I'm just going to have to redevelop the features mostly from scratch.</li> </ul> <p>Those last two options are gonna be hard to manage. </p> <p><strong>Any suggestions on how to port a large number of changes from one branch to another?</strong> When it's not my own in-house code, that is. Here's my initial plan:</p> <ul> <li>Diff between a clean version of 1.1.x and my "dirty" production code</li> <li>Map each line diff to a feature ("That code update is the custom tagging feature, gonna have to port it line by line, and that one over there is the gallery, I can probably install an updated mod.") <em>This would be SOMUCHEASIER if there were a diff tool that generated a consolidated report, instead of having to go through scores of files one at a time.</em> Google and SO searches didn't find a tool like that-- <strong>Is there one?</strong></li> <li>Install a clean 2.0 branch</li> <li>Install the available updated mods</li> <li>Roll up my sleeves and go through my diffs feature by feature (this? is why I need the consolidated diff report. It would be hell to do page by page.) and build them back in.</li> </ul> <p>Any better ideas? (Pointers to release management info are welcome, though of course with the caveat that <em>it's not actually my code</em> so I have limited control.) </p> <p>Otherwise? I fear my options are ditch the custom features (not really feasible) or stay on the old branch. Both suck. Help!</p> <p><strong>tl;dr</strong>: Point me to a diff tool that will do consolidated file-by-file diff reports for entire directories. And/or help me figure out an easier way to migrate my custom code.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USbuzzo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload