[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [linuxtools-dev] Supporting nightly updates for previous release
|
On 05/25/2010 03:12 PM, Chris Aniszczyk wrote:
On Tue, May 25, 2010 at 1:50 PM, Jeff Johnston<jjohnstn@xxxxxxxxxx> wrote:
I was briefly discussing this with Andrew, but thought I would pose the idea
here for comment.
At present, we are building nightly updates from trunk. For the most part,
this isn't a problem. However, when we make any changes that require latest
versions of underlying plugins (e.g. we use a new platform interface or we
switch to requiring latest CDT, Mylyn, etc..), then nightly updates may no
longer apply to the previous release as they don't meet prereqs.
I would like to propose that we support multiple versions of a plugin on the
update site where necessary so that the previous release of Eclipse can
still acquire nightly updates.
So I assume you simply build from trunk using PDE Build (or Athena)?
Have you considered moving to map files as a way to build things? You
would always build from tags that are specified in the map files (this
is how the Eclipse platform team builds things). You branch on
specific releases to support them as need be (e.g., look at some of
the R3_4* branches for the Eclipse platform). You have specific builds
for each maintenance branch you want to support.
Andrew has set the build up to use map files, but we only build the
latest trunk into the nightly update site.
In the end, it really depends how long do you want to support old
releases. Smaller projects generally have the flexibility to only
support the current release (which makes things easier) but as you
grow and become more of a platform... you may need to be considerate
about people running on older versions of Eclipse.
This was another question that I would like to hear comments on. I was
thinking perhaps 6 months to allow users a reasonable time to migrate
and bug fixes to be made so that is possible. At the moment, we have
already switched to Helios nightly updates and Helios isn't officially
out. I haven't made a branch yet so it isn't currently an issue, but to
handle some of the API violation issues, I will have to. So, either I
wait until some time after Helios is out to make the fixes and branch or
otherwise any subsequent fixes won't be available to current users
unless they switch to Helios immediately.
