David M Williams wrote:
Regarding step 1, -
Review your components (plugins) and label them with the cvs tag
"v20041118"
...
I know there was a little discussion
on this already, but guess I missed the conclusion.
Please clarify the need, or if not
one,
then confirm the "make sure all components are versioned" is
more appropriate
first step.
I agree.
Hi committers,
There will be an I-Build on thursday with the label v20041118.
It will be triggered 8 AM EST. Please prepare your components for
this build. Here is a reminder list for the tasks:
- Review your components (plugins) and label them with the cvs tag
"v20041118"
- Review the entries in org.eclipse.wst and org.eclipse.jst
features make sure your plugins are listed if you want it to be
included
in the I-build.
- Review the entries in releng maps make sure your plugins/features
are listed and has the proper label (v20041118).
- All plugins listed in feature.xml must have a corresponding entry in
the map file. Please do not forget to check that all requirements of
your
plugins and their prerequired plugins are listed in build.cfg file. If
not, let me know.
Please take care of the urls in maps/build.cfg file. It must be direct
link to a zip file, and can be download without any redirections.
So use this link junitFileBuildURL=http://download.eclipse.org/downloads/drops/S-3.1M2-200409240800/eclipse-test-framework-3.1M2.zip
instead of junitFileBuildURL=http://download.eclipse.org/downloads/drops/S-3.1M2-200409240800/download.php?dropFile=eclipse-test-framework-3.1M2.zip
Thanks,
Deniz
|