Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Board committer reps  » What's in a noteworthy keyword?
What's in a noteworthy keyword? [message #6118] Wed, 01 August 2007 19:46 Go to next message
Eclipse User
Originally posted by: zx.us.ibm.com

http://eclipse-committer-reps.blogspot.com/2007/08/whats-in- noteworthy-keyword.html
-------------

I remember in the past, as an Eclipse user, looking at the New and
Noteworthy document for each milestone with glee. It was something to
anticipate when each Eclipse milestone was released... you thought to
yourself, what cool stuff will be in this milestone?

Now, as an Eclipse committer, I'm on the side of generating some of
these New and Noteworthy items. I have created a bug requesting that a
new keyword be added to bugzilla called noteworthy. The purpose of this
keyword is three-fold:

* Make it easier for committers to tag what items they think are
noteworthy. A common workflow for committers towards the end of a
release is to scan the bugs fixed and pick and choose noteworthy items.
I think we can improve this.
* In the best interest of transparency, our users (and even our
committers) would like to see where noteworthy items come from and to be
easy to query what's new would be great.
* For people like the EMF team who like to automatically generate
release notes with each release, this can be a way to mark specific bugs
as noteworthy ones.

So, if you're a committer or even a user who think this would be useful,
please comment on the bug. If you're a committer on a project that
doesn't publish these new and noteworthy type of documents, I highly
recommend it as it's something your consumers may enjoy to read.

Cheers,

~ Chris
Re: What's in a noteworthy keyword? [message #6135 is a reply to message #6118] Wed, 01 August 2007 19:55 Go to previous messageGo to next message
Eugene Kuleshov is currently offline Eugene Kuleshov
Messages: 505
Registered: July 2009
Senior Member
Chris,

The problem with noteworthy is that you only see it at the end of
milestone even if you pickup integration build much earlier.

It would be really neat to have blog per project and where could post
entries there tagged as "noteworthy" among with other stuff. At some
point DLTK folks were doing this on their own site. But now that we have
blogs on eclipse.org perhaps that is not unrealistic and then these
entries could be exported and compiled into the release document.

regards,
Eugene


Chris Aniszczyk wrote:
> http://eclipse-committer-reps.blogspot.com/2007/08/whats-in- noteworthy-keyword.html
>
> -------------
>
> I remember in the past, as an Eclipse user, looking at the New and
> Noteworthy document for each milestone with glee. It was something to
> anticipate when each Eclipse milestone was released... you thought to
> yourself, what cool stuff will be in this milestone?
>
> Now, as an Eclipse committer, I'm on the side of generating some of
> these New and Noteworthy items. I have created a bug requesting that a
> new keyword be added to bugzilla called noteworthy. The purpose of
> this keyword is three-fold:
>
> * Make it easier for committers to tag what items they think are
> noteworthy. A common workflow for committers towards the end of a
> release is to scan the bugs fixed and pick and choose noteworthy
> items. I think we can improve this.
> * In the best interest of transparency, our users (and even our
> committers) would like to see where noteworthy items come from and to
> be easy to query what's new would be great.
> * For people like the EMF team who like to automatically generate
> release notes with each release, this can be a way to mark specific
> bugs as noteworthy ones.
>
> So, if you're a committer or even a user who think this would be
> useful, please comment on the bug. If you're a committer on a project
> that doesn't publish these new and noteworthy type of documents, I
> highly recommend it as it's something your consumers may enjoy to read.
>
> Cheers,
>
> ~ Chris
Re: What's in a noteworthy keyword? [message #6150 is a reply to message #6135] Wed, 01 August 2007 20:03 Go to previous messageGo to next message
Eclipse User
Originally posted by: merks.ca.ibm.com

Eugene,

We produce release notes with every published build indicating which
bugzillas have been committed to that build. This is created
automatically by virtue of using the bugzilla number in the commit comment.


Eugene Kuleshov wrote:
> Chris,
>
> The problem with noteworthy is that you only see it at the end of
> milestone even if you pickup integration build much earlier.
>
> It would be really neat to have blog per project and where could post
> entries there tagged as "noteworthy" among with other stuff. At some
> point DLTK folks were doing this on their own site. But now that we
> have blogs on eclipse.org perhaps that is not unrealistic and then
> these entries could be exported and compiled into the release document.
>
> regards,
> Eugene
>
>
> Chris Aniszczyk wrote:
>> http://eclipse-committer-reps.blogspot.com/2007/08/whats-in- noteworthy-keyword.html
>>
>> -------------
>>
>> I remember in the past, as an Eclipse user, looking at the New and
>> Noteworthy document for each milestone with glee. It was something to
>> anticipate when each Eclipse milestone was released... you thought to
>> yourself, what cool stuff will be in this milestone?
>>
>> Now, as an Eclipse committer, I'm on the side of generating some of
>> these New and Noteworthy items. I have created a bug requesting that
>> a new keyword be added to bugzilla called noteworthy. The purpose of
>> this keyword is three-fold:
>>
>> * Make it easier for committers to tag what items they think are
>> noteworthy. A common workflow for committers towards the end of a
>> release is to scan the bugs fixed and pick and choose noteworthy
>> items. I think we can improve this.
>> * In the best interest of transparency, our users (and even our
>> committers) would like to see where noteworthy items come from and to
>> be easy to query what's new would be great.
>> * For people like the EMF team who like to automatically generate
>> release notes with each release, this can be a way to mark specific
>> bugs as noteworthy ones.
>>
>> So, if you're a committer or even a user who think this would be
>> useful, please comment on the bug. If you're a committer on a project
>> that doesn't publish these new and noteworthy type of documents, I
>> highly recommend it as it's something your consumers may enjoy to read.
>>
>> Cheers,
>>
>> ~ Chris
Re: What's in a noteworthy keyword? [message #6165 is a reply to message #6150] Wed, 01 August 2007 20:11 Go to previous messageGo to next message
Eugene Kuleshov is currently offline Eugene Kuleshov
Messages: 505
Registered: July 2009
Senior Member
Ed,

I know that, but it is not the same as new and noteworthy. Also, not
even all Platform project update build notes and some of them are
outdated for about 2 years.

regards,
Eugene


Ed Merks wrote:
> Eugene,
>
> We produce release notes with every published build indicating which
> bugzillas have been committed to that build. This is created
> automatically by virtue of using the bugzilla number in the commit
> comment.
>
>
> Eugene Kuleshov wrote:
>> Chris,
>>
>> The problem with noteworthy is that you only see it at the end of
>> milestone even if you pickup integration build much earlier.
>>
>> It would be really neat to have blog per project and where could
>> post entries there tagged as "noteworthy" among with other stuff. At
>> some point DLTK folks were doing this on their own site. But now that
>> we have blogs on eclipse.org perhaps that is not unrealistic and then
>> these entries could be exported and compiled into the release document.
>>
>> regards,
>> Eugene
>>
>>
>> Chris Aniszczyk wrote:
>>> http://eclipse-committer-reps.blogspot.com/2007/08/whats-in- noteworthy-keyword.html
>>>
>>> -------------
>>>
>>> I remember in the past, as an Eclipse user, looking at the New and
>>> Noteworthy document for each milestone with glee. It was something
>>> to anticipate when each Eclipse milestone was released... you
>>> thought to yourself, what cool stuff will be in this milestone?
>>>
>>> Now, as an Eclipse committer, I'm on the side of generating some of
>>> these New and Noteworthy items. I have created a bug requesting that
>>> a new keyword be added to bugzilla called noteworthy. The purpose of
>>> this keyword is three-fold:
>>>
>>> * Make it easier for committers to tag what items they think are
>>> noteworthy. A common workflow for committers towards the end of a
>>> release is to scan the bugs fixed and pick and choose noteworthy
>>> items. I think we can improve this.
>>> * In the best interest of transparency, our users (and even our
>>> committers) would like to see where noteworthy items come from and
>>> to be easy to query what's new would be great.
>>> * For people like the EMF team who like to automatically
>>> generate release notes with each release, this can be a way to mark
>>> specific bugs as noteworthy ones.
>>>
>>> So, if you're a committer or even a user who think this would be
>>> useful, please comment on the bug. If you're a committer on a
>>> project that doesn't publish these new and noteworthy type of
>>> documents, I highly recommend it as it's something your consumers
>>> may enjoy to read.
>>>
>>> Cheers,
>>>
>>> ~ Chris
Re: What's in a noteworthy keyword? [message #6180 is a reply to message #6165] Wed, 01 August 2007 20:38 Go to previous messageGo to next message
Eclipse User
Originally posted by: merks.ca.ibm.com

Eugene,

No, it's not the same, but if we could highlight things of particular
interest and even find time to add a nice description in the bugzilla
that might be extracted to generate a better report, at least it's a
step in the right direction. For many projects, it's hard to figure out
what's even in each build, as you point out...


Eugene Kuleshov wrote:
> Ed,
>
> I know that, but it is not the same as new and noteworthy. Also, not
> even all Platform project update build notes and some of them are
> outdated for about 2 years.
>
> regards,
> Eugene
>
>
> Ed Merks wrote:
>> Eugene,
>>
>> We produce release notes with every published build indicating which
>> bugzillas have been committed to that build. This is created
>> automatically by virtue of using the bugzilla number in the commit
>> comment.
>>
>>
>> Eugene Kuleshov wrote:
>>> Chris,
>>>
>>> The problem with noteworthy is that you only see it at the end of
>>> milestone even if you pickup integration build much earlier.
>>>
>>> It would be really neat to have blog per project and where could
>>> post entries there tagged as "noteworthy" among with other stuff. At
>>> some point DLTK folks were doing this on their own site. But now
>>> that we have blogs on eclipse.org perhaps that is not unrealistic
>>> and then these entries could be exported and compiled into the
>>> release document.
>>>
>>> regards,
>>> Eugene
>>>
>>>
>>> Chris Aniszczyk wrote:
>>>> http://eclipse-committer-reps.blogspot.com/2007/08/whats-in- noteworthy-keyword.html
>>>>
>>>> -------------
>>>>
>>>> I remember in the past, as an Eclipse user, looking at the New and
>>>> Noteworthy document for each milestone with glee. It was something
>>>> to anticipate when each Eclipse milestone was released... you
>>>> thought to yourself, what cool stuff will be in this milestone?
>>>>
>>>> Now, as an Eclipse committer, I'm on the side of generating some of
>>>> these New and Noteworthy items. I have created a bug requesting
>>>> that a new keyword be added to bugzilla called noteworthy. The
>>>> purpose of this keyword is three-fold:
>>>>
>>>> * Make it easier for committers to tag what items they think
>>>> are noteworthy. A common workflow for committers towards the end of
>>>> a release is to scan the bugs fixed and pick and choose noteworthy
>>>> items. I think we can improve this.
>>>> * In the best interest of transparency, our users (and even our
>>>> committers) would like to see where noteworthy items come from and
>>>> to be easy to query what's new would be great.
>>>> * For people like the EMF team who like to automatically
>>>> generate release notes with each release, this can be a way to mark
>>>> specific bugs as noteworthy ones.
>>>>
>>>> So, if you're a committer or even a user who think this would be
>>>> useful, please comment on the bug. If you're a committer on a
>>>> project that doesn't publish these new and noteworthy type of
>>>> documents, I highly recommend it as it's something your consumers
>>>> may enjoy to read.
>>>>
>>>> Cheers,
>>>>
>>>> ~ Chris
Re: What's in a noteworthy keyword? [message #6194 is a reply to message #6180] Wed, 01 August 2007 21:19 Go to previous messageGo to next message
Eugene Kuleshov is currently offline Eugene Kuleshov
Messages: 505
Registered: July 2009
Senior Member
Yea, that could be an option, though noteworthy things could have some
graphics, etc. That is why I thought blog-based approach is more
attractive to the end users (not to mention that you could subscribe to
its rss). It could be also easier to manage to the project owners (i.e.
in case if particular feature can't be represented with a single bug).

regards,
Eugene


Ed Merks wrote:
> Eugene,
>
> No, it's not the same, but if we could highlight things of particular
> interest and even find time to add a nice description in the bugzilla
> that might be extracted to generate a better report, at least it's a
> step in the right direction. For many projects, it's hard to figure
> out what's even in each build, as you point out...
>
> Eugene Kuleshov wrote:
>> Ed,
>>
>> I know that, but it is not the same as new and noteworthy. Also, not
>> even all Platform project update build notes and some of them are
>> outdated for about 2 years.
>>
>> regards,
>> Eugene
>>
Re: What's in a noteworthy keyword? [message #6208 is a reply to message #6194] Wed, 01 August 2007 22:10 Go to previous messageGo to next message
Eclipse User
Originally posted by: zx.us.ibm.com

Eugene, my main interest is in making it easier for committers to tag
such things and even plan for noteworthy items. The current workflow for
most projects (if they even publish such things) is to at the end of a
release to go through bugzilla and come up with a document. I don't like
this approach as a committer. I would like to see this be more
transparent and even offer the ability to be queried.

In PDE, we generally have a good idea of what we want to be an N&N item
for each milestone and this would allow us to plan better. Furthermore,
it would allow users to query back in time if they were curious when a
certain feature came around.

This is also useful for people like EMF who generate their release notes
by hand.

It may not be the perfect solution, but I think it's a step in the right
direction.

Cheers,

~ Chris
Re: What's in a noteworthy keyword? [message #6223 is a reply to message #6208] Wed, 01 August 2007 22:20 Go to previous messageGo to next message
Eclipse User
Originally posted by: codeslave.ca.ibm.com

.... and it would allow us to generate our N&N automagically [1]. Instead
of having to write a blog and update a wiki and update bugzilla, you do
it in one place (bugzilla) and generate the content as needed.

As to the religious preference between wiki and blog, I'd vote for wiki
because it's in one central place rather than somewhere on
foo.blogspot.com or dev.eclipse.org/blogs/foo

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=198021#c9

I'm all for it, especially if someone other than me gets to write the
bugzilla2N&N generator. ;-)

Nick
Re: What's in a noteworthy keyword? [message #6238 is a reply to message #6208] Wed, 01 August 2007 22:24 Go to previous messageGo to next message
Eugene Kuleshov is currently offline Eugene Kuleshov
Messages: 505
Registered: July 2009
Senior Member
Chris,

You don't really have to explain this to me. But with your
clarifications it sounds like you still have to manually prepare that
document from bugzilla items, while querying tagged entries would allow
to automate that...

regards,
Eugene


Chris Aniszczyk wrote:
> Eugene, my main interest is in making it easier for committers to tag
> such things and even plan for noteworthy items. The current workflow
> for most projects (if they even publish such things) is to at the end
> of a release to go through bugzilla and come up with a document. I
> don't like this approach as a committer. I would like to see this be
> more transparent and even offer the ability to be queried.
>
> In PDE, we generally have a good idea of what we want to be an N&N
> item for each milestone and this would allow us to plan better.
> Furthermore, it would allow users to query back in time if they were
> curious when a certain feature came around.
>
> This is also useful for people like EMF who generate their release
> notes by hand.
>
> It may not be the perfect solution, but I think it's a step in the
> right direction.
>
> Cheers,
>
> ~ Chris
Re: What's in a noteworthy keyword? [message #6253 is a reply to message #6223] Wed, 01 August 2007 22:40 Go to previous messageGo to next message
Eugene Kuleshov is currently offline Eugene Kuleshov
Messages: 505
Registered: July 2009
Senior Member
Hmm. Just out of curiosity, how would you stick screenshots into
bugzilla to be consumed by such generator? Or the idea is to drop all
the pictures in a favor of rough text?

With blogs it doesn't really matter where they are located, using rss
they can be aggregated from pretty much anywhere and by its nature it is
also more structured information then bugzilla entries. Another
advantage is that they can be subscribed directly too.

Anyways, I am somehow new to the concept of planning new and
noteworthy and been more interested in early notification about these
features. Still not convinced that bugzilla would be the best option,
because early adopters would have to dig trough each bug report if they
need to understand how particular feature works (but not how it is
implemented). So, the noise ratio won't be very good.

regards,
Eugene


Nick Boldt wrote:
> ... and it would allow us to generate our N&N automagically [1]. Instead
> of having to write a blog and update a wiki and update bugzilla, you do
> it in one place (bugzilla) and generate the content as needed.
>
> As to the religious preference between wiki and blog, I'd vote for wiki
> because it's in one central place rather than somewhere on
> foo.blogspot.com or dev.eclipse.org/blogs/foo
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=198021#c9
>
> I'm all for it, especially if someone other than me gets to write the
> bugzilla2N&N generator. ;-)
>
> Nick
>
Re: What's in a noteworthy keyword? [message #6268 is a reply to message #6253] Wed, 01 August 2007 23:56 Go to previous message
Eclipse User
Originally posted by: merks.ca.ibm.com

Eugene,

I'm not suggesting it would be a good way, but it's possible to attach
an image to a bugzilla and then reference it. Of course the bugzilla
could reference a link to anywhere as well. The whole point of Chris'
feature request is to provide more automation in terms of tracking the
things that are new capabilities to which to pay particular attention.
In EMF-land we are notoriously bad at making folks aware of all the new
and cool things that we make available because we're just too busy on
the next feature and then we forget all about all the cool stuff a few
weeks later, so a marker like this couldn't hurt even if it doesn't help
a lot...


Eugene Kuleshov wrote:
>
> Hmm. Just out of curiosity, how would you stick screenshots into
> bugzilla to be consumed by such generator? Or the idea is to drop all
> the pictures in a favor of rough text?
>
> With blogs it doesn't really matter where they are located, using rss
> they can be aggregated from pretty much anywhere and by its nature it
> is also more structured information then bugzilla entries. Another
> advantage is that they can be subscribed directly too.
>
> Anyways, I am somehow new to the concept of planning new and
> noteworthy and been more interested in early notification about these
> features. Still not convinced that bugzilla would be the best option,
> because early adopters would have to dig trough each bug report if
> they need to understand how particular feature works (but not how it
> is implemented). So, the noise ratio won't be very good.
>
> regards,
> Eugene
>
>
> Nick Boldt wrote:
>> ... and it would allow us to generate our N&N automagically [1]. Instead
>> of having to write a blog and update a wiki and update bugzilla, you do
>> it in one place (bugzilla) and generate the content as needed.
>>
>> As to the religious preference between wiki and blog, I'd vote for wiki
>> because it's in one central place rather than somewhere on
>> foo.blogspot.com or dev.eclipse.org/blogs/foo
>>
>> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=198021#c9
>>
>> I'm all for it, especially if someone other than me gets to write the
>> bugzilla2N&N generator. ;-)
>>
>> Nick
>>
Re: What's in a noteworthy keyword? [message #560463 is a reply to message #6118] Wed, 01 August 2007 19:55 Go to previous message
Eugene Kuleshov is currently offline Eugene Kuleshov
Messages: 505
Registered: July 2009
Senior Member
Chris,

The problem with noteworthy is that you only see it at the end of
milestone even if you pickup integration build much earlier.

It would be really neat to have blog per project and where could post
entries there tagged as "noteworthy" among with other stuff. At some
point DLTK folks were doing this on their own site. But now that we have
blogs on eclipse.org perhaps that is not unrealistic and then these
entries could be exported and compiled into the release document.

regards,
Eugene


Chris Aniszczyk wrote:
> http://eclipse-committer-reps.blogspot.com/2007/08/whats-in- noteworthy-keyword.html
>
> -------------
>
> I remember in the past, as an Eclipse user, looking at the New and
> Noteworthy document for each milestone with glee. It was something to
> anticipate when each Eclipse milestone was released... you thought to
> yourself, what cool stuff will be in this milestone?
>
> Now, as an Eclipse committer, I'm on the side of generating some of
> these New and Noteworthy items. I have created a bug requesting that a
> new keyword be added to bugzilla called noteworthy. The purpose of
> this keyword is three-fold:
>
> * Make it easier for committers to tag what items they think are
> noteworthy. A common workflow for committers towards the end of a
> release is to scan the bugs fixed and pick and choose noteworthy
> items. I think we can improve this.
> * In the best interest of transparency, our users (and even our
> committers) would like to see where noteworthy items come from and to
> be easy to query what's new would be great.
> * For people like the EMF team who like to automatically generate
> release notes with each release, this can be a way to mark specific
> bugs as noteworthy ones.
>
> So, if you're a committer or even a user who think this would be
> useful, please comment on the bug. If you're a committer on a project
> that doesn't publish these new and noteworthy type of documents, I
> highly recommend it as it's something your consumers may enjoy to read.
>
> Cheers,
>
> ~ Chris
Re: What's in a noteworthy keyword? [message #560470 is a reply to message #6135] Wed, 01 August 2007 20:03 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26138
Registered: July 2009
Senior Member
Eugene,

We produce release notes with every published build indicating which
bugzillas have been committed to that build. This is created
automatically by virtue of using the bugzilla number in the commit comment.


Eugene Kuleshov wrote:
> Chris,
>
> The problem with noteworthy is that you only see it at the end of
> milestone even if you pickup integration build much earlier.
>
> It would be really neat to have blog per project and where could post
> entries there tagged as "noteworthy" among with other stuff. At some
> point DLTK folks were doing this on their own site. But now that we
> have blogs on eclipse.org perhaps that is not unrealistic and then
> these entries could be exported and compiled into the release document.
>
> regards,
> Eugene
>
>
> Chris Aniszczyk wrote:
>> http://eclipse-committer-reps.blogspot.com/2007/08/whats-in- noteworthy-keyword.html
>>
>> -------------
>>
>> I remember in the past, as an Eclipse user, looking at the New and
>> Noteworthy document for each milestone with glee. It was something to
>> anticipate when each Eclipse milestone was released... you thought to
>> yourself, what cool stuff will be in this milestone?
>>
>> Now, as an Eclipse committer, I'm on the side of generating some of
>> these New and Noteworthy items. I have created a bug requesting that
>> a new keyword be added to bugzilla called noteworthy. The purpose of
>> this keyword is three-fold:
>>
>> * Make it easier for committers to tag what items they think are
>> noteworthy. A common workflow for committers towards the end of a
>> release is to scan the bugs fixed and pick and choose noteworthy
>> items. I think we can improve this.
>> * In the best interest of transparency, our users (and even our
>> committers) would like to see where noteworthy items come from and to
>> be easy to query what's new would be great.
>> * For people like the EMF team who like to automatically generate
>> release notes with each release, this can be a way to mark specific
>> bugs as noteworthy ones.
>>
>> So, if you're a committer or even a user who think this would be
>> useful, please comment on the bug. If you're a committer on a project
>> that doesn't publish these new and noteworthy type of documents, I
>> highly recommend it as it's something your consumers may enjoy to read.
>>
>> Cheers,
>>
>> ~ Chris
Re: What's in a noteworthy keyword? [message #560477 is a reply to message #6150] Wed, 01 August 2007 20:11 Go to previous message
Eugene Kuleshov is currently offline Eugene Kuleshov
Messages: 505
Registered: July 2009
Senior Member
Ed,

I know that, but it is not the same as new and noteworthy. Also, not
even all Platform project update build notes and some of them are
outdated for about 2 years.

regards,
Eugene


Ed Merks wrote:
> Eugene,
>
> We produce release notes with every published build indicating which
> bugzillas have been committed to that build. This is created
> automatically by virtue of using the bugzilla number in the commit
> comment.
>
>
> Eugene Kuleshov wrote:
>> Chris,
>>
>> The problem with noteworthy is that you only see it at the end of
>> milestone even if you pickup integration build much earlier.
>>
>> It would be really neat to have blog per project and where could
>> post entries there tagged as "noteworthy" among with other stuff. At
>> some point DLTK folks were doing this on their own site. But now that
>> we have blogs on eclipse.org perhaps that is not unrealistic and then
>> these entries could be exported and compiled into the release document.
>>
>> regards,
>> Eugene
>>
>>
>> Chris Aniszczyk wrote:
>>> http://eclipse-committer-reps.blogspot.com/2007/08/whats-in- noteworthy-keyword.html
>>>
>>> -------------
>>>
>>> I remember in the past, as an Eclipse user, looking at the New and
>>> Noteworthy document for each milestone with glee. It was something
>>> to anticipate when each Eclipse milestone was released... you
>>> thought to yourself, what cool stuff will be in this milestone?
>>>
>>> Now, as an Eclipse committer, I'm on the side of generating some of
>>> these New and Noteworthy items. I have created a bug requesting that
>>> a new keyword be added to bugzilla called noteworthy. The purpose of
>>> this keyword is three-fold:
>>>
>>> * Make it easier for committers to tag what items they think are
>>> noteworthy. A common workflow for committers towards the end of a
>>> release is to scan the bugs fixed and pick and choose noteworthy
>>> items. I think we can improve this.
>>> * In the best interest of transparency, our users (and even our
>>> committers) would like to see where noteworthy items come from and
>>> to be easy to query what's new would be great.
>>> * For people like the EMF team who like to automatically
>>> generate release notes with each release, this can be a way to mark
>>> specific bugs as noteworthy ones.
>>>
>>> So, if you're a committer or even a user who think this would be
>>> useful, please comment on the bug. If you're a committer on a
>>> project that doesn't publish these new and noteworthy type of
>>> documents, I highly recommend it as it's something your consumers
>>> may enjoy to read.
>>>
>>> Cheers,
>>>
>>> ~ Chris
Re: What's in a noteworthy keyword? [message #560485 is a reply to message #6165] Wed, 01 August 2007 20:38 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26138
Registered: July 2009
Senior Member
Eugene,

No, it's not the same, but if we could highlight things of particular
interest and even find time to add a nice description in the bugzilla
that might be extracted to generate a better report, at least it's a
step in the right direction. For many projects, it's hard to figure out
what's even in each build, as you point out...


Eugene Kuleshov wrote:
> Ed,
>
> I know that, but it is not the same as new and noteworthy. Also, not
> even all Platform project update build notes and some of them are
> outdated for about 2 years.
>
> regards,
> Eugene
>
>
> Ed Merks wrote:
>> Eugene,
>>
>> We produce release notes with every published build indicating which
>> bugzillas have been committed to that build. This is created
>> automatically by virtue of using the bugzilla number in the commit
>> comment.
>>
>>
>> Eugene Kuleshov wrote:
>>> Chris,
>>>
>>> The problem with noteworthy is that you only see it at the end of
>>> milestone even if you pickup integration build much earlier.
>>>
>>> It would be really neat to have blog per project and where could
>>> post entries there tagged as "noteworthy" among with other stuff. At
>>> some point DLTK folks were doing this on their own site. But now
>>> that we have blogs on eclipse.org perhaps that is not unrealistic
>>> and then these entries could be exported and compiled into the
>>> release document.
>>>
>>> regards,
>>> Eugene
>>>
>>>
>>> Chris Aniszczyk wrote:
>>>> http://eclipse-committer-reps.blogspot.com/2007/08/whats-in- noteworthy-keyword.html
>>>>
>>>> -------------
>>>>
>>>> I remember in the past, as an Eclipse user, looking at the New and
>>>> Noteworthy document for each milestone with glee. It was something
>>>> to anticipate when each Eclipse milestone was released... you
>>>> thought to yourself, what cool stuff will be in this milestone?
>>>>
>>>> Now, as an Eclipse committer, I'm on the side of generating some of
>>>> these New and Noteworthy items. I have created a bug requesting
>>>> that a new keyword be added to bugzilla called noteworthy. The
>>>> purpose of this keyword is three-fold:
>>>>
>>>> * Make it easier for committers to tag what items they think
>>>> are noteworthy. A common workflow for committers towards the end of
>>>> a release is to scan the bugs fixed and pick and choose noteworthy
>>>> items. I think we can improve this.
>>>> * In the best interest of transparency, our users (and even our
>>>> committers) would like to see where noteworthy items come from and
>>>> to be easy to query what's new would be great.
>>>> * For people like the EMF team who like to automatically
>>>> generate release notes with each release, this can be a way to mark
>>>> specific bugs as noteworthy ones.
>>>>
>>>> So, if you're a committer or even a user who think this would be
>>>> useful, please comment on the bug. If you're a committer on a
>>>> project that doesn't publish these new and noteworthy type of
>>>> documents, I highly recommend it as it's something your consumers
>>>> may enjoy to read.
>>>>
>>>> Cheers,
>>>>
>>>> ~ Chris
Re: What's in a noteworthy keyword? [message #560489 is a reply to message #6180] Wed, 01 August 2007 21:19 Go to previous message
Eugene Kuleshov is currently offline Eugene Kuleshov
Messages: 505
Registered: July 2009
Senior Member
Yea, that could be an option, though noteworthy things could have some
graphics, etc. That is why I thought blog-based approach is more
attractive to the end users (not to mention that you could subscribe to
its rss). It could be also easier to manage to the project owners (i.e.
in case if particular feature can't be represented with a single bug).

regards,
Eugene


Ed Merks wrote:
> Eugene,
>
> No, it's not the same, but if we could highlight things of particular
> interest and even find time to add a nice description in the bugzilla
> that might be extracted to generate a better report, at least it's a
> step in the right direction. For many projects, it's hard to figure
> out what's even in each build, as you point out...
>
> Eugene Kuleshov wrote:
>> Ed,
>>
>> I know that, but it is not the same as new and noteworthy. Also, not
>> even all Platform project update build notes and some of them are
>> outdated for about 2 years.
>>
>> regards,
>> Eugene
>>
Re: What's in a noteworthy keyword? [message #560497 is a reply to message #6194] Wed, 01 August 2007 22:10 Go to previous message
Chris Aniszczyk is currently offline Chris Aniszczyk
Messages: 674
Registered: July 2009
Senior Member
Eugene, my main interest is in making it easier for committers to tag
such things and even plan for noteworthy items. The current workflow for
most projects (if they even publish such things) is to at the end of a
release to go through bugzilla and come up with a document. I don't like
this approach as a committer. I would like to see this be more
transparent and even offer the ability to be queried.

In PDE, we generally have a good idea of what we want to be an N&N item
for each milestone and this would allow us to plan better. Furthermore,
it would allow users to query back in time if they were curious when a
certain feature came around.

This is also useful for people like EMF who generate their release notes
by hand.

It may not be the perfect solution, but I think it's a step in the right
direction.

Cheers,

~ Chris
Re: What's in a noteworthy keyword? [message #560503 is a reply to message #6208] Wed, 01 August 2007 22:20 Go to previous message
Nick Boldt is currently offline Nick Boldt
Messages: 480
Registered: July 2009
Senior Member
.... and it would allow us to generate our N&N automagically [1]. Instead
of having to write a blog and update a wiki and update bugzilla, you do
it in one place (bugzilla) and generate the content as needed.

As to the religious preference between wiki and blog, I'd vote for wiki
because it's in one central place rather than somewhere on
foo.blogspot.com or dev.eclipse.org/blogs/foo

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=198021#c9

I'm all for it, especially if someone other than me gets to write the
bugzilla2N&N generator. ;-)

Nick
Re: What's in a noteworthy keyword? [message #560510 is a reply to message #6208] Wed, 01 August 2007 22:24 Go to previous message
Eugene Kuleshov is currently offline Eugene Kuleshov
Messages: 505
Registered: July 2009
Senior Member
Chris,

You don't really have to explain this to me. But with your
clarifications it sounds like you still have to manually prepare that
document from bugzilla items, while querying tagged entries would allow
to automate that...

regards,
Eugene


Chris Aniszczyk wrote:
> Eugene, my main interest is in making it easier for committers to tag
> such things and even plan for noteworthy items. The current workflow
> for most projects (if they even publish such things) is to at the end
> of a release to go through bugzilla and come up with a document. I
> don't like this approach as a committer. I would like to see this be
> more transparent and even offer the ability to be queried.
>
> In PDE, we generally have a good idea of what we want to be an N&N
> item for each milestone and this would allow us to plan better.
> Furthermore, it would allow users to query back in time if they were
> curious when a certain feature came around.
>
> This is also useful for people like EMF who generate their release
> notes by hand.
>
> It may not be the perfect solution, but I think it's a step in the
> right direction.
>
> Cheers,
>
> ~ Chris
Re: What's in a noteworthy keyword? [message #560518 is a reply to message #6223] Wed, 01 August 2007 22:40 Go to previous message
Eugene Kuleshov is currently offline Eugene Kuleshov
Messages: 505
Registered: July 2009
Senior Member
Hmm. Just out of curiosity, how would you stick screenshots into
bugzilla to be consumed by such generator? Or the idea is to drop all
the pictures in a favor of rough text?

With blogs it doesn't really matter where they are located, using rss
they can be aggregated from pretty much anywhere and by its nature it is
also more structured information then bugzilla entries. Another
advantage is that they can be subscribed directly too.

Anyways, I am somehow new to the concept of planning new and
noteworthy and been more interested in early notification about these
features. Still not convinced that bugzilla would be the best option,
because early adopters would have to dig trough each bug report if they
need to understand how particular feature works (but not how it is
implemented). So, the noise ratio won't be very good.

regards,
Eugene


Nick Boldt wrote:
> ... and it would allow us to generate our N&N automagically [1]. Instead
> of having to write a blog and update a wiki and update bugzilla, you do
> it in one place (bugzilla) and generate the content as needed.
>
> As to the religious preference between wiki and blog, I'd vote for wiki
> because it's in one central place rather than somewhere on
> foo.blogspot.com or dev.eclipse.org/blogs/foo
>
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=198021#c9
>
> I'm all for it, especially if someone other than me gets to write the
> bugzilla2N&N generator. ;-)
>
> Nick
>
Re: What's in a noteworthy keyword? [message #560525 is a reply to message #6253] Wed, 01 August 2007 23:56 Go to previous message
Ed Merks is currently offline Ed Merks
Messages: 26138
Registered: July 2009
Senior Member
Eugene,

I'm not suggesting it would be a good way, but it's possible to attach
an image to a bugzilla and then reference it. Of course the bugzilla
could reference a link to anywhere as well. The whole point of Chris'
feature request is to provide more automation in terms of tracking the
things that are new capabilities to which to pay particular attention.
In EMF-land we are notoriously bad at making folks aware of all the new
and cool things that we make available because we're just too busy on
the next feature and then we forget all about all the cool stuff a few
weeks later, so a marker like this couldn't hurt even if it doesn't help
a lot...


Eugene Kuleshov wrote:
>
> Hmm. Just out of curiosity, how would you stick screenshots into
> bugzilla to be consumed by such generator? Or the idea is to drop all
> the pictures in a favor of rough text?
>
> With blogs it doesn't really matter where they are located, using rss
> they can be aggregated from pretty much anywhere and by its nature it
> is also more structured information then bugzilla entries. Another
> advantage is that they can be subscribed directly too.
>
> Anyways, I am somehow new to the concept of planning new and
> noteworthy and been more interested in early notification about these
> features. Still not convinced that bugzilla would be the best option,
> because early adopters would have to dig trough each bug report if
> they need to understand how particular feature works (but not how it
> is implemented). So, the noise ratio won't be very good.
>
> regards,
> Eugene
>
>
> Nick Boldt wrote:
>> ... and it would allow us to generate our N&N automagically [1]. Instead
>> of having to write a blog and update a wiki and update bugzilla, you do
>> it in one place (bugzilla) and generate the content as needed.
>>
>> As to the religious preference between wiki and blog, I'd vote for wiki
>> because it's in one central place rather than somewhere on
>> foo.blogspot.com or dev.eclipse.org/blogs/foo
>>
>> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=198021#c9
>>
>> I'm all for it, especially if someone other than me gets to write the
>> bugzilla2N&N generator. ;-)
>>
>> Nick
>>
Previous Topic:What's in a noteworthy keyword?
Next Topic:Fine-tuning the Eclipse Committer Experience
Goto Forum:
  


Current Time: Fri Oct 24 07:01:41 GMT 2014

Powered by FUDForum. Page generated in 0.02683 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software