> I only ever see the Platform/JDT N&N in web page form. How is this web
page constructed? Is it just done by hand, or is it somehow automatically
generated from some data source?

We write it by hand as HTML.


On Mon, Feb 2, 2015 at 3:25 PM, Wayne Beaton <wa...@eclipse.org> wrote:

>  I agree with Dani. Each project's N&N should be project-specific.
>
> I only ever see the Platform/JDT N&N in web page form. How is this web
> page constructed? Is it just done by hand, or is it somehow automatically
> generated from some data source?
>
> The ideal, I think, would be to have a common form for feature information
> that is maintained by each project based, perhaps, around the features that
> they provide. With something like this in place, we'd have a fighting
> chance of aggregating it in a meaningful/useful manner and keeping it
> up-to-date.
>
> e.g. some kind of record with a title, html fragment with zero or more
> images, and a "since" tag that we can compare against the feature version
> to determine what features are new. We could use this to generate a
> complete feature list and a N&N list.
>
> Maybe this is just an XML file that we keep with each feature.
>
> Thoughts?
>
> Wayne
>
>
>
> On 02/02/15 05:35 AM, Daniel Megert wrote:
>
> > I think the correct solution would be to extend the purpose of the
> Platform N&N to include newsitems from the EPP side.
>
> No, that is not the correct solution. The EPP/main download side can have
> and advertise a joint N&N.
>
> Dani
>
>
>
> From:        Lars Vogel <lars.vo...@vogella.com> <lars.vo...@vogella.com>
> To:        Cross project issues <cross-project-issues-dev@eclipse.org>
> <cross-project-issues-dev@eclipse.org>
> Date:        02.02.2015 11:15
> Subject:        Re: [cross-project-issues-dev] Joint N&N page for the
> release train
> Sent by:        cross-project-issues-dev-boun...@eclipse.org
> ------------------------------
>
>
>
> Hi Marcel,
>
> I think the correct solution would be to extend the purpose of the
> Platform N&N to include newsitems from the EPP side.
>
> Best regards, Lars
>
> On Mon, Feb 2, 2015 at 11:11 AM, Marcel Bruch <
> *marcel.br...@codetrails.com* <marcel.br...@codetrails.com>> wrote:
> Greetings cross-projects,
>
> I’d like to get your thoughts about a joint N&N page for Mars Milestones.
>
> The platform maintains a N&N page [1] for changes on the Platform/JDT/PDE.
> All press releases, blogs and tweets about new milestones are pointing to
> this page and as such it is the most prominent place to present new
> features, what’s new and upcoming in Eclipse.
>
> However, IMHO there are much more noteworthy things to talk about. For
> instance, the addition of the automated error reporting in all EPP packages
> is such a noteworthy item but it cannot be published on that page because
> it does not belong to the SDK. I guess many projects have interesting N&N
> as well. While larger projects with a community/ popular webpage will
> certainly write a blog post about their new features. Smaller ones with no
> prominent website or large community lack such a space. In addition,
> bloggers etc. will certainly not browse all project blogs to find all N&Ns.
>
> Thus I wonder whether we should have a joint N&N page for the whole
> release train where every participating project could put, say, up to 3
> items per Milestone release with a picture and a short paragraph (as the
> SDK already does).
>
> What do others think?
>
>
> Marcel
>
>
>
> P.S.: FWIW, every EPP package download page *has* a N&N link in the side
> menu where EPP packages can add their N&N links. However, it’s not used
> much and likely is not very popular (at least I assume that b/c I noticed
> it the very first time today).
>
> [1] *https://www.eclipse.org/eclipse/news/4.5/M5/*
> <https://www.eclipse.org/eclipse/news/4.5/M5/>
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> *cross-project-issues-dev@eclipse.org*
> <cross-project-issues-dev@eclipse.org>
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> *https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev*
> <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>
>
>
>
> --
> Geschäftsführer
>
> 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.vo...@vogella.com*
> <lars.vo...@vogella.com>, Web: *http://www.vogella.com*
> <http://www.vogella.com/>_______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> 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 listcross-project-issues-...@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, 
> visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> --
> Wayne Beaton
> @waynebeaton
> The Eclipse Foundation
> [image: EclipseCon 2015] <http://www.eclipsecon.org/na2015>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>



-- 
Geschäftsführer

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.vo...@vogella.com, Web:
http://www.vogella.com
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to