Re: [eclipse-pmc] Photon (4.8) Release Review Material

["Mike Wilson" <Mike_Wilson@xxxxxxxxxx>]

> 30 or 80% got delivered. In the end those tagged with partially delivered did not get delivered.

I can definitively say that in the past, on the PMC, I remember cases where we did not treat it as that cut and dried. As to specific cases, the only one I saw was the one I mentioned -- from you're reply it looks like the image that showed it did not get included in the message; the item was:

Improving Debugging Usability
Several Debugging usability features - bug 498469
PARTIALLY DELIVERED in 4.8

My point was just that any item called "improving ... usability" will *never* be 100% completed. To quote your example, for me (for this kind of item), 80% delivered == delivered (with follow on work in the next release).

> The nature issue can't be resolved as there is no protocol to react to nature changes at the moment.

Sure, but if we haven't got any idea how we could get past the state where we might be leaving people's installs "requiring further extensive and non-obvious configuration changes", it seems like maybe we should have held off on the feature. Of course, it's my fault for discovering this only now. Regardless, we should look at building in the mechanisms that are required, in a future release, so that plugin builders can react.

> promote the new futures with the new Tips feature

That would be part of it. I was thinking more along the lines of finding new ways to support people who were new to Eclipse, Java development or both. IDK, maybe there aren't many of those left. :-P

McQ.

"Daniel Megert" ---2018/05/28 12:43:50---I'd have to go back to each project lead to check whether 30 or 80% got  delivered. In the end those

From:        "Daniel Megert" <daniel_megert@xxxxxxxxxx>
To:        eclipse-pmc@xxxxxxxxxxx
Date:        2018/05/28 12:43
Subject:        Re: [eclipse-pmc] Photon (4.8) Release Review Material
Sent by:        eclipse-pmc-bounces@xxxxxxxxxxx

---

I'd have to go back to each project lead to check whether 30 or 80% got delivered. In the end those tagged with partially delivered did not get delivered. Do you have a special item in mind that needs work?

The nature issue can't be resolved as there is no protocol to react to nature changes at the moment.

I hope that we can promote the new futures with the new Tips feature in the future. Also, most of the new features are either in the Tips & Trick or the N&N document.

Dani



From:        "Mike Wilson" <Mike_Wilson@xxxxxxxxxx>
To:        eclipse-pmc@xxxxxxxxxxx
Date:        28.05.2018 18:29
Subject:        Re: [eclipse-pmc] Photon (4.8) Release Review Material
Sent by:        eclipse-pmc-bounces@xxxxxxxxxxx

---

Overall, I am +1. 

Some thoughts...

One minor point In the platform debug plan, where I see:


I'm fine with labelling things like this "partially delivered", if the benefits couldn't be realized because some particular enhancements didn't get finished. However, if the set of enhancements that *were* delivered would be separately beneficial, then I would trend toward declaring the item DELIVERED, even if there is additional work to be done next release. The reason is that, with something as open ended as "improve usability" there is *always* more work that can be done. 

In the N&N, where it talks about modifying project natures it says "some natures may not properly handle manual addition/removal, so using this can lead to some inconsistencies in those cases". For my own edification, what is the plan for getting those cases fixed? (I'm thinking of, for example, what Apple does when you start a 32-bit app now, where it says "the developer need to update this application...", or something like that).

Also, reading through the JDT N&N reminds me once again of how awesome a powertool it is for Java developers! I couldn't help but wonder though, if I was a Java noob, would I be able to find and configure all the myriad of options that are available. It might make sense to take another round of thinking about the new user XP (doc, guides, progressive disclosure, etc.) in future releases.

McQ.

"Daniel Megert" ---2018/05/28 11:32:19---Dear PMC Members, please review the Photon (4.8) release review material and respond with

From: "Daniel Megert" <daniel_megert@xxxxxxxxxx>
To: eclipse-pmc@xxxxxxxxxxx
Date: 2018/05/28 11:32
Subject: [eclipse-pmc] Photon (4.8) Release Review Material
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

---

Dear PMC Members,

please review the Photon (4.8) release review materialand respond with feedback to this list. As agreed before, this comes in a minimal version. Please respond whether you approve or decline the review by May 30,

As already with the previous releases, the IP Log is no longer attached to the release review record. You can review it here: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=16480.
NOTE: There seems to be a problem with a very old bundle that never caused an issue but has no CQ. Alex, I also tried to add you to that CQ, but it said: "CC:akurtakov@xxxxxxxxx did not match anything"

The review itself is tracked by bug 535136: [release] Eclipse Photon (4.8).

Thanks,
Dani_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc

[attachment "16012192.jpg" deleted by Daniel Megert/Zurich/IBM] [attachment "graycol.gif" deleted by Daniel Megert/Zurich/IBM] _______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc