Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 500939

Summary: Create New and Noteworthy for Neon.1
Product: Community Reporter: David Williams <david_williams>
Component: Cross-ProjectAssignee: Wayne Beaton <wayne.beaton>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: eclipse
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description David Williams CLA 2016-09-06 14:38:43 EDT
Now that "new features" can be in update releases, we should allow for a new document that points out the "Noteworthy" features that are in the update release. 

The Neon "noteworthy" document is at 

https://www.eclipse.org/neon/noteworthy/

I suspect the best way to manage this is to create a new document, smaller than the initial one, with only what is new in Neon.1 (and that smaller document can contain a link back to "neon/botworthy" if someone comes along much later and what's to read about the entire Neon stream. But, the author of this document is free to be as creative as they would like to be. :) 

See also bug 497426. That "Linux Tools" section should be incorporate into the original, IMHO.
Comment 1 David Williams CLA 2016-09-06 14:41:58 EDT
Wayne, I *think* you did the original and assume you will do the "updates". 

If that is incorrect, please re-assign to the person who should be reponsible for the overall editing. I assume, though, that projects are respoinsible for making suggestions on what they consider new and noteworthy so the author's job is mainly filtering that input for consistency of "worthiness" and consisten look. 

Please clarify if that is not the case.
Comment 2 Wayne Beaton CLA 2016-09-07 13:49:45 EDT
The current document has a section on sources at the end. I'm thinking that we can just append Neon.1 documents produced by the project teams to that list and extract out the end-user focused entries into the main document (perhaps with a "since Neon.1" qualifer).

IMHO, a single document that lists everything is more useful to the customer.
Comment 3 Holger Voormann CLA 2016-09-28 03:37:07 EDT
Video: "Eclipse Neon.1: 4:00-minute demo of 10 improvements"
https://youtu.be/hW0ENpGcP34
Comment 4 Wayne Beaton CLA 2016-09-28 10:43:58 EDT
(In reply to Holger Voormann from comment #3)
> Video: "Eclipse Neon.1: 4:00-minute demo of 10 improvements"
> https://youtu.be/hW0ENpGcP34

I've embedded the video. Nice work.

I can add additional content if given pointers. I'll troll around for them a bit, but actually giving them to me is the best bet for getting them in the content.
Comment 5 Wayne Beaton CLA 2016-11-03 14:28:40 EDT
I'm going to declare victory.

I've captured the process for creating this documentation in the Simultaneous Release Requirements Appendix document.

https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements/Appendix#New_and_Noteworthy
Comment 6 David Williams CLA 2016-11-28 13:14:59 EST
To cross-reference, I have tweaked the "Final Daze" document to include a section to "Provide input for overall New and Noteworthy". See

https://wiki.eclipse.org/Neon/Final_Daze#Provide_input_for_overall_New_and_Noteworthy

which points to another URL for "how to" information: 

https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements/Appendix#New_and_Noteworthy