I am developing in ActionScript 2 and ActionScript 3 at the same time. I decided to branch the project when I got a stable build. However, upon finding a bug during conversion (Flex Builder 2 rules), I had to document the change (quick note in Notepad) and go back and fix it in the AS2 codebase.
Upon a 4 hour development stint in the AS2 codebase, I found 3 bugs and fixed them in 3 different classes. I forgot to document them. Now, I’m contemplating the best way to handle a forked build in the allotted timeframe.
It seems the best thing to do is get the AS2 codebase to a working point, freeze it, and then start converting the existing AS2 codebase from that point forward to AS3. The mantra “garbage in, garbage out” seems to come into play here. Starting with an already flawed codebase seems a guarenteed failure scenario. I’ve read about a successful venture using the Subversion branch feature. They had to fork the build since they wanted to try something else, found out it wasn’t such a good idea, and removed the build without affecting the main codebase.
The key now becomes being able to successfully do a time estimate so you know when you have to freeze so you allot yourself enough time to convert the code base, test, and get it to a freezing point as well.
Anyone had experience writing in dual-languages for the same codebase before? How did you handle it?