John, As one of the 'lurkers' that is subscribed to this list to follow and track the progress of the wtp-tools project, I for one think that these types of build smoke tests/preliminary results are very much of interest. This easily lets me know what is actually worthy of bothering to download.
Granted, I don't need to track the daily automated builds. However the weekly I-builds, related smoke tests, and milestone builds I am very interested to track as a rough indicator of quality. Lastly, the very high volume of the wtp-releng list makes it very unmanageable for me as the signal to noise ratio is just too low. Your suggestion of just announcing declared builds tells me nothing of the quality of the build and is already provided by the wtp builds page which I already know (usually) happens on a weekly basis. Just my 2 cents. -Darrell -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Arthorne Sent: Thursday, January 12, 2006 2:50 AM To: General discussion of project-wide or architectural issues. Subject: Re: [wtp-dev] Weekly 101 M-build declared: M200601102004 Tue,10 Jan 2006 -- 20:04 (UTC) I suspect there are many people who listen to the wtp-dev mailing list because they are interested in hearing discussion of general project-wide or architectural issues, but are not interested in these frequent discussions of build issues. While announcing declared (fully tested) builds might be of wider interest, the discussion of smoke tests and build issues seems to produce a lot of clutter that many of us could do without. Might I suggest that discussion of builds and test results be moved to the wtp-releng mailing list rather than the general wtp-dev? That way those with an interest in builds can still follow along, but the wider community can tune it out if they don't want to hear it. John _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
