Re: 150009 - release65 stopper
Petr Blaha <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.reviewers |
|---|---|
| Message-ID | <[email protected]> |
Mark Dey wrote: > Petr, this is a data loss bug which seems to warrant a respin. The bug is definitely stopper and must be fixed. Can the > fix get in along with the new graphic and still allow us to deliver a > Go/No go on Monday? Yes, we plan to push the fix in 65 clone after QE verification and wait for new branding. The new build will start at 2pm tomorrow and ready for testing on Mon morning. The GO/NO GO on Monday is still on the track. Petr > > - Mark > > > On Nov 6, 2008, at 6:07 AM, Jiri Skrivanek wrote: > >> Please review fix of issue 150009. It should be fixed in 6.5: >> >> http://www.netbeans.org/issues/show_bug.cgi?id=150009 >> >> * Description of the bug (including IZ #) >> >> If java.io.File.listFiles() returns null, filesystems mistakenly fire >> FILE_DELETED events and potentional listeners (like versioning >> support) delete affected files. null from listFiles() can be returned >> if I/O operation fails (e.g. 'too may files open' error). >> >> * Impact assessment i.e. why it is a showstopper? >> >> It is data loss. User files can be deleted. >> >> * Risk assessment i.e. why is it safe? >> >> The patch only handles state when 'listFiles() == null' which should >> not happen normally. Other functionallity is intact. >> >> * Confirmation of peer code review and QE verification of fix >> >> Tomas Hurka created the patch and I reviewed it. >> >> * Changeset info (for reviewing diffs) >> >> http://hg.netbeans.org/main/rev/f5128636599a >> >> Jirka >