Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-releng] Status and outlook for WTP 3.2.4

There have been no new bug fixes on the maintenance stream since last week. But, the observant will notice there was an additional build, on 4/29 [1]. (I say "the observant" on purpose, to exclude myself, since I'd forgotten about this until I started looking closely this evening ... apologies to those of you who I said "there's been no new bugs requested for our final build" when you were probably asking me if there were any other builds).

The difference from 4/28 to 4/29 was a follow-through to the approved bug 343770 [2] which we added in a last minute respin. Nick asked and I agreed he should fix the test feature versioning related to that bug fix, and he added some logging to a unit test that failed. A diff on the map files [3] show these were the only changes from 4/28 to 4/29 build.

I suggest we just declare this latest, 4/29 build, with no formal smoke testing. I think we are all simply doing "final testing" until we release so I'm sure most will want to do final testing on this build, but I'm confident the non-unit-test portions are identical. I guess as an alternative, we could just skip the versioning fix since just in a test feature, but seems cleaner to declare it, and little risk. As another alternative we could do a formal smoke test, but we will soon be asking for formal release sign-off, so seems like a lot of paper work.

According to our schedule [4], this week is our "final build" on 5/6, and next week we will formally release on 5/13. The final week is supposed to be "quite week", with no more builds, but I'm sure we would at least consider a new build if a serious regression was discovered, since we want to maintain good, stable quality.

Let me know if others have different points of view, but if there's no objections before our 2:00 status meeting, we'll go with this "just declare it" strategy. Later, next week, we'll begin a formal "sign off" on the release, just to document all Project Leads agree we are done and the 4/29 build is the build to release.

Thank you,


[1] http://build.eclipse.org/webtools/committers/wtp-R3.2.4-M/20110429183427/M-3.2.4-20110429183427/

[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=343770

[3] $ diff M-3.2.4-20110428170154.directory.txt M-3.2.4-20110429183427.directory.txt

    < feature@xxxxxxxxxxxxxxx.web_tests.feature=v201012072038, ... sourceediting/features/org.eclipse.jst.web_tests.feature
    > feature@xxxxxxxxxxxxxxx.web_tests.feature=v201104291759, ... sourceediting/features/org.eclipse.jst.web_tests.feature

    < plugin@xxxxxxxxxxxxxxxxxxxxxxxx.tests=v201104281428, ... sourceediting/tests/org.eclipse.jst.jsp.core.tests
    > plugin@xxxxxxxxxxxxxxxxxxxxxxxx.tests=v201104291757, ... sourceediting/tests/org.eclipse.jst.jsp.core.tests

[4] http://wiki.eclipse.org/WTP_2011-04-28#3.2.4_Schedule


Back to the top