Re: [orion-dev] how is Bugzilla used ?

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

We don't currently use bugzilla for tracking
"plan items" for Orion. All of the implementation details are
covered there, but you don't get the high level plan view from bugzilla.
Our plan is tracked in the standard Eclipse project portal. You can see
the current early draft of the Orion 9 plan here:

https://projects.eclipse.org/projects/eclipse.orion/releases/9.0/plan





From:      
 Max Rydahl Andersen
<manderse@xxxxxxxxxx>
To:      
 Orion developer discussions
<orion-dev@xxxxxxxxxxx>
Date:      
 04/23/2015 02:18 PM
Subject:    
   Re: [orion-dev]
how is Bugzilla used ?
Sent by:    
   orion-dev-bounces@xxxxxxxxxxx

---

I think a simple query for which issues haven't moved
for over a year should be skimmed for important stuff and close as won't
fix with comment about reopening If still a concern for the reporter could
help. 

Btw. Which bz query is used on the release plan ? Couldn't
find link for it. 

/max
http://about.me/maxandersen


On 23 Apr 2015, at 17:34, John Arthorne <John_Arthorne@xxxxxxxxxx>
wrote:

Mark's summary of how it is used is
accurate. I use a similar approach, using a separate email account to help
me manage the volume. There is definitely a bunch of ancient junk in there,
which I find happens with any successful open source project. The old stuff
was all triaged as a reasonable idea or valid bug at the time it was entered,
but over time may have become stale, irrelevant, or invalid. Sorting and/or
querying by most recently modified date helps you get a more useful picture.
I sometimes go through the old backlog and do some pruning but haven't
been able to keep up with the volume lately. We've been talking recently
about ideas for cleaning that up - any ideas you have in that are are welcome!

John 



From:        Mark
Macdonald <mamacdon@xxxxxxxxx>
To:        Orion
developer discussions <orion-dev@xxxxxxxxxxx>
Date:        04/23/2015
11:01 AM 
Subject:        Re:
[orion-dev] how is Bugzilla used ? 
Sent by:        orion-dev-bounces@xxxxxxxxxxx

---

I have subscribed to e-mail notifications in every Orion bugzilla component,
so I get emails for every new bug or comment. I then archive those emails
and search them for keywords when I need to find bugs.  
Admittedly this won't work for a new user, since you won't have that email
history. If there's a set of bugs that I need to monitor closely, I create
a custom bugzilla query that returns only those bug IDs, and bookmark it.

Most Orion components have a reasonably-sized backlog which can be viewed
as a list: JS Tools, Editor, Server, Doc, Releng, Node -- these are all
OK-ish. The big problem is Client: it's a dumping ground that contains
lots of ancient junk.

Maybe we need an automated WONTFIX pass for anything with no recent activity
in (say) the last year?

Mark 

On Thu, Apr 23, 2015 at 6:21 AM, Max Rydahl Andersen <manderse@xxxxxxxxxx>
wrote: 
Hi,

While looking into orion we were looking into current state of bugs in
bugzilla, mainly starting from the "View open bugs" and "summarise
bugs" links at https://projects.eclipse.org/projects/eclipse.orion/developer

The 1500+ open bugs seems a bit high and some seems really old and maybe
not even relevant anymore.

We were wondering how you do triaging on these since there are not *that*
many components.

Any tips/inisights on how you triage this and how you suggest newcomers
get an idea of where to sort/look
would be great!

Thanks,
/max
http://about.me/maxandersen
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/orion-dev
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/orion-dev

_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/orion-dev_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/orion-dev