We do always declare with the most recent
build, under the assumption someone released something for a good reason,
that is safe, and should be in the build.
[unless someone says not to, of course]
The only bundle change in the 100 failing
build-test run was this plugin
But, there was another change I forgot
to mention ... I have re-enabled signing on our 3.1 builds
(since milestones should be signed,
for best, realistic testing). Hopefully it's not _that_ which is
causing the failures.
We'll find out soon.
And, as I write this, there is even
another build running, with the following plugins/features changed.
these two were to remove some JUnit
tests with fail routinely (and bugs have been opened to fix later)
I suspect these were changed to fix
I think we need to crisp-up our weekly
cycle some and Helen and I have been discussing some ideas ...
to be discussed later, maybe in a week
or two, depending on what's technically feasible
(but suggestions welcome).
but in the mean time, if you release
a change after Wednesday night, say after Wednesday midnight Eastern time,
please post a note here to wtp-releng@xxxxxxxxxxx
so everyone knows what's going on.
Neil Hauge <neil.hauge@xxxxxxxxxx>
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
09/25/2008 05:07 PM
[wtp-releng] JPT failures in latest
There are 100 failing JPT tests in the latests 3.1
build. This was a
result of one test failing that caused a cascade of failures. No
changes were made for this build, and not sure if we were even
considering this build for M2, but wanted to let people know about it.
We hope to have these test issues resolved for the first M3 build.