I've discussed with the Tools PMC, and others, and we agree -- at this point in time -- this would be worth a respin to pick up the fix, for improved "out of the box" user experience (instead of crashing, in some circumstances).
I say "this point in time" only because we do have a little buffer built-in to the plan. (A similar issue, if found at this time next week, would likely not be approved, since could be fixed from project's own update site). So, despite the extra work, we do what a quality result, and WindowBuilder is used in two popular EPP packages, so ... we will rebuild. Thanks, From: Mark R Russell <[email protected]> To: David M Williams/Raleigh/IBM@IBMUS, Cross project issues <[email protected]>, Cc: Eric Clayberg <[email protected]> Date: 06/11/2015 12:55 PM Subject: Re: [cross-project-issues-dev] WIndowBuilder Sent by: [email protected] Sorry for the delay have been rebuilding and testing, and I am in a closed notebook class all day today Here is the tracking bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469924 The build is done and staged The change is in Gerrit: https://git.eclipse.org/r/50041 and was submitted. On Thu, Jun 11, 2015 at 12:52 PM Mark R Russell <[email protected]> wrote: Sorry for the delay I have been rebuilding and testing, and I am i in a closed notebook class all day today Here is the tracking bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469924 The build is done and staged The change is in Gerrit: https://git.eclipse.org/r/50041 waiting for tests to complete. On Thu, Jun 11, 2015 at 7:17 AM David M Williams < [email protected]> wrote: Mark R Russell <[email protected]> wrote on 06/11/2015 07:02:51 AM: > From: Mark R Russell <[email protected]> > To: Cross project issues <[email protected]>, > Cc: Eric Clayberg <[email protected]>, David M Williams/Raleigh/IBM@IBMUS > Date: 06/11/2015 07:03 AM > Subject: Re: WIndowBuilder > > We did find an issue and we have a fix. I need to get the code > signed and in the aggregation. I'll let you know when it is done. Once you "let us know when done", be sure to include bug number that describes the issue well. And, ideally the nature of the fix. Include some justification why the "risk is work the gain". That is, there's risk in any rebuild ... both of the build not working for reasons completely unrelated to your fix, or some really weird, unexpected side effects. In other words, at this point, we don't respin for just any one :) But, naturally, we all have an interest in shipping high quality, but, you've got to justify why it's worth rocking the whole train. Could you, for example, make a fix available on your own update site, to be available at same time we release? Or, would that not work well for this case? (such as, would damage existing code, before they had the update?) All that said ... I (we all) do want to help you out, here ... but, we have to have some limit at some point, so ask that you justify it along the above lines so we can apply same criteria to everyone. Thanks, _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
