| [imp-dev] Branching in SVN to move forward with new API |
| Hi All, I'd like to branch the repository for a 0.2.* line of work that will be API incompatible with 0.1.*. Once the branch is in place, I'd like to host builds of the 0.2 branch in a separate part of the IMP update site, say, http://download.eclipse.org/technology/imp/updates/0.2. This way, we can maintain compatibility with current users of the 0.1 line, while freeing ourselves to make breaking API changes. By hosting 0.2 builds in a separate spot, users won't need to worry about picking up incompatible code. In particular, as long as no one mixes code from the two sites, we don't need to worry that existing feature/plugin dependency constraints would accept the newer 0.2 features/plugins. Comments? -- Cheers, - Bob ------------------------------------------------- Robert M. Fuhrer Research Staff Member Programming Technologies Dept. IBM T.J. Watson Research Center IMP Project Lead (http://www.eclipse.org/imp) X10: Productivity for High-Performance Parallel Programming (http://x10-lang.org) |