Guess you're tired. ;-)
The idea is to put the 0.2 stuff on a *separate* update site (i.e. a somewhat different URL but still at eclipse.org), so existing users' installations won't even see the new stuff. Unless, that is, they explicitly add that new site to their configuration, which would be inadvisable of course.
On Apr 12, 2010, at 6:29 PM, Jurgen Vinju wrote: Good plan. We're not putting 0.2 stuff on the update site I presume? On Mon, Apr 12, 2010 at 4:02 PM, Robert M. Fuhrer < rfuhrer@xxxxxxxxxxxxxx> wrote: 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
|
