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


I like to start from ideal and work back to realistic.

Realistically, we don't have a proper product manager at this point in time, and we don't have extra engineering cycles. Extracting data from what we already have and prescribing particular formats for a move-forward strategy are likely the best we can do.

And that, I think, can still be a big win.

I like Ian's top 10 features posts as well. However, I believe that the optics of having a proper aggregated N&N document will be a big win in terms of how the community regards Eclipse.


On 02/02/15 12:23 PM, Mickael Istria wrote:
On 02/02/2015 06:19 PM, Doug Schaefer wrote:

From: Lars Vogel <lars.vogel@xxxxxxxxxxx>
> 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.

Efficient, yes. But effective at producing content that users/customers may be interested in and help sell them on your product without getting lost in the tragedy of the commons? To be honest, I think a N&N for the entire release train that isn’t managed by a single person will be a disaster.
Ian (Bull)'s top 10 features for a release train are IMO a good global N&N and give good visibility to the coolest new IDE features.
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

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

Wayne Beaton
The Eclipse Foundation

Back to the top