Re: [epp-dev] Package update testing

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

Thx for your support Eric.
The basic thing that everyone can do is use p2 to move from I-build to I-build, or M-build to M-build by updating, the platform update site is http://download.eclipse.org/eclipse/updates/3.5-I-builds
For package users the same hold, if you try to update between each build, this will help find the corner cases. However at this stage this is not possible because we are missing the repository containing the metadata of each package. I believe that the creation of this metadata and its availability is the topic of tomorrow's call.

Note that updating from Ganymede to Galileo is not supported (for either of these cases)

PaScaL

Eric Rizzo ---04/27/2009 10:45:59 PM---Pascal Rapicault wrote:

From:	Eric Rizzo <eclipse-mail@xxxxxxxxxxxx>
To:	Eclipse Packaging Project <epp-dev@xxxxxxxxxxx>
Date:	04/27/2009 10:45 PM
Subject:	Re: [epp-dev] Package update testing

---

Pascal Rapicault wrote:
> Given that it is likely that people will upgrade to the SR1 release. To 
> make sure we are on the right track for this, I would like that we setup 
> our builds and various servers (including Galileo interim release) to 
> allow for the update path to be tested.

I agree that this is VERY important. I suspect that many of the 
user-reported problems which plagued p2 in Ganymede could have avoided 
the GA release had there been more opportunity for update testing in the 
milestones. Let's do whatever is necessary to avoid making the same 
mistake with Galileo.

What can the "outsiders" (ie, non-commiters) do to help with this?

Eric
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev