Re: [platform-releng-dev] Stable Build Update Sites

[Dean_Roberts@xxxxxxxxxx]

We are currently banging our heads against a seemingly simple but annoying problem that prevents us from doing this.  The problem is basically a naming one.

Currently the HEAD stream of Eclipse is labeled as 2.1.0.  In order to get update manager to update Eclipses we would have to increment this number.  On our test update site we do this by appending the CVS version tags of each feature as a fourth part.  So the "test" update site has versions 2.1.0.x where .x changes with each build.

The problem is, when we finally release 2.1.0 update manager considers this a "lower" version than any 2.1.0.x so we would have no way of updating anybody from the last stable build before a major release to the major release.

So a "sort of" solution for your immediate problem could be to take updates from our "test" update site keeping in mind that when Eclipse 2.1.0 is finally officially released you will not be able to use update manager to upgrade to it.

In the meantime we are trying to solve this problem in the large.

The URL of the test update site is:

update.eclipse.org/testUpdates

Each integration build is put on this server. 

...Dean...

Andrew B Mccullough/Charlotte/IBM@IBMUS Sent by: platform-releng-dev-admin@xxxxxxxxxxx 01/13/2003 02:47 PM Please respond to platform-releng-dev

To:        platform-releng-dev@xxxxxxxxxxx         cc:                 Subject:        [platform-releng-dev] Stable Build Update Sites

Hello all,

I am curious why stable builds are not posted to an Update site.
Obviously, the "real" (official) update site should be reserved for updates
to the releases to support products and users on the official release
builds, but it seems reasonable to me that a second update site for
development could be created and used for (at least) stable builds.  I have
Eclipse installed on at least 3 computers, and I like to stay current with
the stable builds, and doing that right now is a bit difficult.   I also
work with some people that enjoy using the newer builds but are not
necessarily famliar with the structure of eclipse installations (such as
how to move add-on plugins to the new version), workspaces, etc, and this
would provide an easy way to help them upgrade.

The Update manager is a great tool, and I think this would 1) encourage the
community to stay current and help with testing/providing feedback on new
stable builds, and 2) get people used to using the (excellent) Update
manager to upgrade their Eclipse installation.

Besides my own wish to be able to use Update Manager for stable builds,
there seems to be a large number of "How do I upgrade?" posts on the
eclipse.tools newsgroup, and this would certainly provide a clear answer.

-Andrew

-------------------------------------------------------------------------
Andrew B. McCullough
Advisory I/T Specialist
Object Technology Group, IBM Global Services
(704)594-2258 [OTG  Office] [794-2258  TieLine]
(704)957-3794 [Mobile Phone]

mccull1@xxxxxxxxxx

_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev