|Re: [eclipse.org-planning-council] Request for re-spin on behalf of the MPC project|
More serious is the oomph issue.That is a feature that is forcefully enabled right now which has definite issues
and will cause grief and loss of user settings. WTP already requested it, but here it goes again https://bugs.eclipse.org/bugs/show_bug.cgi?id=470430Note latest comments from Eike and that its found affecting other packages beyond WTP. Any preference that are stored as a blob/list gets overwritten by oomph even though
you disabled the recorder. /max
I tested multiple versions of the MPC today.In M6  the D&D feature didn't work today and threw some exceptions that I didn't investigate. It could have been anything, e.g. a change in the webservices API, and I wouldn't use this version to draw any conclusions.M7  shows the same behaviour as the RC builds and the final build of the packages. In all cases, the Finish and the Confirm button stay disabled initially. This is in line with the code change that caused this and hadbeen pushed to Git 3 months ago.My first conclusion is that the D&D feature isn't popular, otherwise this glitch had been detected earlier. This is no wonder because (a) D&D isn't used very often from web pages to applications, and (b) it is much easier to use the MPC client itself to look for new plug-ins and to install it directly from there. That's workaround number 1: Use the MPC itself. It hasbeen working perfectly in all of my tests.And what will a user do when the buttons are disabled? The chance is reallyhigh that in this case he or she will try to disable/enable one of thecheckboxes which solves the problem by triggering an update to the buttons.That's workaround number 2.And we shouldn't forget that SR1 is only 3 months away, that's about the duration that this bug exists. If this is too long there are other low-riskoptions, too, that can be discussed.I think there is no reason to put the release at risk with a respin, or torisk a delay of the release. Thanks, Markus  http://archive.eclipse.org/technology/epp/downloads/release/mars/M6/eclipse-cpp-mars-M6-linux-gtk-x86_64.tar.gz  http://archive.eclipse.org/technology/epp/downloads/release/mars/M7/eclipse-cpp-mars-M7-linux-gtk-x86_64.tar.gz On 19 June 2015 at 02:28, Doug Schaefer <dschaefer@xxxxxxx> wrote:+1 for finding a way to automate this so that we don’t have to decidebetween the burden on Markus and David and the burden on our users. It would also be good to understand why we’re finding so many majorquality problems so late. And as an adopter and as a user, I’m not happy we always decide to skimp on quality to make the schedule. This is why I neverrecommend people take the June release.I also wonder with more frequent releases, we wouldn't hinge so much on this June release. That way we could cut content to save quality with thepromise of the content landing with quality 3 months later. Doug. From: <eclipse.org-planning-council-bounces@xxxxxxxxxxx> on behalf of Ian Bull <irbull@xxxxxxxxxxxxxxxxx> Reply-To: Eclipse Planning Council < eclipse.org-planning-council@xxxxxxxxxxx> Date: Thursday, June 18, 2015 at 6:06 PM To: Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>, Eclipse Planning Council <eclipse.org-planning-council@xxxxxxxxxxx>Subject: Re: [eclipse.org-planning-council] Request for re-spin on behalfof the MPC project A respin is not easy. It adds significant work (and stress) to Markusand David. This bug does not seem severe enough to slip for, nor does itseem fair to ask David and Markus to give up their weekend to fix. Cheers, Ian On Thu, Jun 18, 2015 at 11:04 PM, Mike Milinkovich < mike.milinkovich@xxxxxxxxxxx> wrote:Markus, I completely understand your frustration. Every one of these means abunch of work that falls on you and David's shoulders. After we get through this, we should discuss what we can do to alleviate that going forward.But our users are important, and our user experience is important.Marketplace was once an experiment, but now it is a large part of how ourusers experience Eclipse. We did not make this request lightly. On 18/06/2015 4:31 PM, Markus Knauer wrote: What's the next project requesting a respin? Sorry. A (very) frustrated, MarkusOn 18 June 2015 at 22:26, Chris Aniszczyk <caniszczyk@xxxxxxxxx> wrote:+1 it's a great feature and especially if we're hinging on a lot of marketing for this On Thu, Jun 18, 2015 at 3:22 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:Greetings Planning Council.The MPC project has uncovered a significant bug. There is discussionbelow and more in the cited bug.The TL;DR is that we are hanging a lot of press and potential for good will on the ability to drag and drop features from web pages and the Eclipse Marketplace site, so this really need to work. Further, thisfeature is important to the Marketplace ecosystem and will have a significant impact on perception of overall usability of Eclipse.I hereby a request a respin of the simultaneous release on behalf ofthe Technology PMC. Wayne-------- Forwarded Message -------- Subject: Request for re-spin Date:Thu, 18 Jun 2015 15:11:21 -0400 From: Ian Skerrett <ian.skerrett@xxxxxxxxxxx> <ian.skerrett@xxxxxxxxxxx> To: david_williams@xxxxxxxxxx, Wayne Beaton <wayne@xxxxxxxxxxx><wayne@xxxxxxxxxxx>, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx><mike.milinkovich@xxxxxxxxxxx>, Carsten Reckord <reckord@xxxxxxxx> <reckord@xxxxxxxx>, Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx> <mknauer@xxxxxxxxxxxxxxxxx> David,We have found a critical bug in Marketplace Client (MPC) that breaks the drag and drop feature of MPC. Carsten has fixed the bug and a patch isavailable. https://bugs.eclipse.org/bugs/show_bug.cgi?id=470485 Unfortunately, the workarounds are not intuitive from a usabilityperspective and the drag and drop feature is important for MPC and the overall ecosystem. For instance, we plan to promote the 'early access'Java 9 support through a drag and drop feature. For these reasons, I'd like to request a re-spin of Mars. Is thissomething I should post on cross-projects or is there another process Ishould use._______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-councilIMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you mustcontact emo@xxxxxxxxxxx to request removal.-- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource _______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-councilIMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you mustcontact emo@xxxxxxxxxxx to request removal._______________________________________________ eclipse.org-planning-council mailing list eclipse.org-planning-council@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-councilIMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
Back to the top