[wtp-releng] a test update site is ready for 2.0.3 candidate

[David M Williams <david_williams@xxxxxxxxxx>]

I've made a test update site, at 

http://download.eclipse.org/webtools/milestones/site.xml

Note, the name 'milestones' name in
the URL is arbitrary ... just fit the auto-scripts to go ahead and use
that. 

This site has exactly same as what the
official 'updates' site is, with the 2.0.3 release added. 

I've tested the basics and it seems
ok, (that is, no obvious version number problems, etc. the process did
work ... I did not test the functionality of the resulting install). 

With WTP 2.0.2 installed, you should
be able to test "update existing features" ... IF you use a policy
file, as described in 
http://wiki.eclipse.org/WTP_Patches_for_Release_2.0.2#Testing_the_patch

I used a policy file with contents of

<?xml version="1.0" encoding="UTF-8"?>
<update-policy>
  <url-map pattern="org.eclipse.wst" url="">http://download.eclipse.org/webtools/milestones/site.xml"/>
  <url-map pattern="org.eclipse.jst" url="">http://download.eclipse.org/webtools/milestones/site.xml"/>
  <url-map pattern="org.eclipse.jpt" url="">http://download.eclipse.org/webtools/milestones/site.xml"/>
  <url-map pattern="*" url="">
</update-policy>

And, having that on my local files system, used the following in the install/updates preferences
file:///temp/testPolicySite.xml


For those teams that haven't completed their smoke tests yet (Server and JSF teams) it might be nice if you tried it using the update process.

In an ideal world, we'd have a formal test from all teams (using the test update site) but since everyone is already being "over tested" today, I'm fine leaving it up to each teams discretion on whether or not they want to test this that this update site includes the fixes they expect. (It is pretty likely it does ... it would just be testing against really odd errors in build scripts or similar).

If I hear no objections, as soon as smoke tests page is complete, I'll copy files to appropriate places, wait awhile to be sure replication/mirroring has started, and then formally declared "released".

Thanks everyone.