Time to branch off 3.3 [message #13754] |
Sat, 05 April 2008 08:34 |
|
Hi,
Eclipse 3.3 and Eclipse 3.4 has some significant differences. The P2 replacement or the Update
Manager is perhaps the most significant one for Buckminster since we want to exploit a lot of the
new features but there are other subtle differences as well that makes it very hard to maintain one
code-branch that is functional for both Eclipse versions. I therefore propose that we create a new
branch named Platform-3.3.x in our SVN.
Initially, the proposed branch will be empty. The following will happen for projects where we need
to maintain a special code-branch in order to stay backward compatible:
1. Dependencies that are rendered incompatible in Eclipse 3.4 will be annotated with version ranges
that excludes those versions (i.e. version ranges with upper bounds).
2. The project will be checked in and then copied to the Platform-3.3.x branch.
3. On the trunk, dependencies that are rendered incompatible in Eclipse 3.3 will be annotated with
version ranges that excludes those versions. The upper bounds are removed.
4. On the trunk, the project version will bump from 1.0.0 to 1.1.0.
The buckminster.cquery will change to use projects from the Platform-3.3.x branch in favor of the
trunk components. The buckminster-dev.cquery will remain unchanged and will hence continue to use
the trunk exclusively.
We must also maintain two update sites, one for 3.3 and one for 3.4. The latter will serve as the
source for our Ganymede participation.
If you have no objections to this, I'd like to execute on the above on Monday morning, CET. Needless
to say, any outstanding changes should be checked in by then.
Regards,
Thomas Hallgren
|
|
|
Re: Time to branch off 3.3 [message #13774 is a reply to message #13754] |
Sat, 05 April 2008 11:37 |
Henrik Lindberg Messages: 2509 Registered: July 2009 |
Senior Member |
|
|
+1
henrik
Thomas Hallgren wrote:
> Hi,
> Eclipse 3.3 and Eclipse 3.4 has some significant differences. The P2
> replacement or the Update Manager is perhaps the most significant one
> for Buckminster since we want to exploit a lot of the new features but
> there are other subtle differences as well that makes it very hard to
> maintain one code-branch that is functional for both Eclipse versions. I
> therefore propose that we create a new branch named Platform-3.3.x in
> our SVN.
>
> Initially, the proposed branch will be empty. The following will happen
> for projects where we need to maintain a special code-branch in order to
> stay backward compatible:
>
> 1. Dependencies that are rendered incompatible in Eclipse 3.4 will be
> annotated with version ranges that excludes those versions (i.e. version
> ranges with upper bounds).
> 2. The project will be checked in and then copied to the Platform-3.3.x
> branch.
> 3. On the trunk, dependencies that are rendered incompatible in Eclipse
> 3.3 will be annotated with version ranges that excludes those versions.
> The upper bounds are removed.
> 4. On the trunk, the project version will bump from 1.0.0 to 1.1.0.
>
> The buckminster.cquery will change to use projects from the
> Platform-3.3.x branch in favor of the trunk components. The
> buckminster-dev.cquery will remain unchanged and will hence continue to
> use the trunk exclusively.
>
> We must also maintain two update sites, one for 3.3 and one for 3.4. The
> latter will serve as the source for our Ganymede participation.
>
> If you have no objections to this, I'd like to execute on the above on
> Monday morning, CET. Needless to say, any outstanding changes should be
> checked in by then.
>
> Regards,
> Thomas Hallgren
|
|
|
Powered by
FUDForum. Page generated in 0.02141 seconds