Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Joint N&N page for the release train

> Ideally, we have a product/project manager who puts all this together. Don’t let engineers do your marketing :).

-1, having worked for a large software company in the past, I think the current platform approach of having the developer describe his development is much more efficient.

On Mon, Feb 2, 2015 at 6:04 PM, Doug Schaefer <dschaefer@xxxxxxx> wrote:
Ideally, we have a product/project manager who puts all this together. Don’t let engineers do your marketing :).


From: Wayne Beaton <wayne@xxxxxxxxxxx>
Organization: The Eclipse Foundation
Reply-To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: Monday, February 2, 2015 at 10:53 AM
To: "cross-project-issues-dev@xxxxxxxxxxx" <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] Joint N&N page for the release train

Okay. Avoidance of more work is a requirement. Forget all that silliness about a common XML file format and putting extra files in features.


On 02/02/15 10:03 AM, Daniel Megert wrote:
For us it would mean more work, which I'd like to avoid. Having one document easily allows to tools to e.g. check for XHTML validity, and help fix such issues. If the document is generated out of pieces, then it can be a tedious task to get to a generated document that is valid. The extension point doc is such an example: the text for the elements is entered in the extension point editor in separate fields, and during build a document is generated. If there are errors, it's hard to detect and fix them. Also, spell checking a single document is easier than doing the same over different fragments.

Another point is, that the N&N of a release is not simply the collection of the milestone N&Ns. We e.g. put the new Quick Fixes under one item for the release, or a feature that got developed over several milestones with entries in the corresponding milestone N&Ns will have to be collapsed into a single entry.

I'd like to keep our approach for our project, since it works well for us, and produces good quality N&N documents. If other projects want to try out something new where the N&N is generated, and provide feedback about how it worked for them, that's of course fine for me too.


Wayne Beaton
The Eclipse Foundation
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx, Web:

Back to the top