When should Java SE 6u10 beta perform an auto-update? | Java.net

My pages	Projects	Communities	java.net

Get Involved About java.net Request a Project Publicize your Project Submit Content java-net Project Java.net Enhancements Site Help Report Inappropriate Content Get Informed Articles Blogs Events java.net Online Books java.net Archives Get Connected java.net Forums Wiki Javapedia People Partners Jobs RSS Feeds Java User Groups Search Web and Projects: Online Books: java.net on MarkMail: Advanced Search
		When should Java SE 6u10 beta perform an auto-update? Every new build 36% (135 votes) Only at Milestone builds (Release Candidate and General Availability) 46% (173 votes) Something else (please comment) 3% (12 votes) Never 15% (55 votes) Total votes: 375 » Login or register to post comments 376 visits Printer-friendly version 6u10 verus 6u6 Submitted by jwenting on Fri, 2008-05-16 05:37. how can you know which beta a potential bug you find is related to if the software goes ahead and updates itself? Login or register to post comments 6u10 verus 6u6 Submitted by swpalmer on Fri, 2008-05-16 05:58. If you are testing a beta you better be aware of it and know what you are doing. If you can't figure out what JRE you are testing you shouldn't be testing a beta in the first place. Login or register to post comments 6u10 verus 6u6 Submitted by prunge on Fri, 2008-05-23 00:38. Consider these sequence of events: I am writing a bug report I type 'java -version' into console to fill in version number on bug report Java autoupdate updates itself to newest beta I run the test case for the bug report unaware of the version update Bug report with results from test case filed using incorrect version number Given the time between 'java -version' and running of the test case is typically small (seconds) this scenario is unlikely but it is possible. But I guess we could always turn autoupdate off before doing a bug report. Login or register to post comments 6u10 verus 6u6 Submitted by jwenting on Sun, 2008-05-18 12:13. if it's installing updates on its own you can't know what you're testing because the software under testing is changing itself while you're testing it. Login or register to post comments 6u10 verus 6u6 Submitted by swpalmer on Tue, 2008-05-20 08:01. Nothing is suggesting that the JRE you are running your application on will change while you are running your application. The JRE will be constant for any particular run of your application. Error logs should identify the JRE version easily. Or you can just check with "java -version" when you notice a problem. Login or register to post comments Autoupdate testing Submitted by prunge on Fri, 2008-05-23 00:48. I guess autoupdate needs user testing too, but I would be one to turn it off immediately so I can be sure of the version I am using when submitting bug reports and testing my own stuff under the new version. Login or register to post comments manual update Submitted by nopjn on Sun, 2008-05-18 10:38. And why not add an Advanced button in the options to reached a series of button to "Update to the Latest Release" or "Update to the latest beta build" ? Login or register to post comments The poll description may be misleading Submitted by mbien on Fri, 2008-05-16 13:18. IMO the builds should be updating automatically to the next buld until the final version is reached and beta builds should update to next beta builds until...final. (this is how firefox works - at least for betas) After this point the updater should fall back into the "update to next final release" mode. Why: - people using builds are most likely devs or very technology interested users which want to be up to date - people using betas are a little bit less interested in the bleeding edge but still want the update to the next beta since it is more stable - the average user should be clear ;-) ... Login or register to post comments Why not let the user choose? Submitted by lilianne_blaze on Fri, 2008-05-16 08:59. Why not add an option to Control Panel \ Java \ Update - "Every new build" / "RCs and Final versions" / "Final versions only"? It should be pretty easy to implement. Login or register to post comments Test early test often Submitted by swpalmer on Fri, 2008-05-16 05:56. It's beta - the latest code should be in the hands of the beta testers always until it hits general release. There is no point to testing obsolete code. Login or register to post comments