[haiku-development] Re: Trac: setting milestone of fixed tickets, upvoting duplicates
- From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 9 Jul 2020 20:19:28 +0200
On Thu, Jul 09, 2020 at 07:14:56PM +0200, Humdinger wrote:
Hi there!
First, am I correct that everyone who's closing a ticket as fixed should
mark it for the next milestone (Beta3 currently)?
nielx started doing that during the work on beta2 and I think it's a
good idea as it helps see what's fixed in the next release and better
see our progress. So, I vote +1 to that.
Second, I propose to upvote the original ticket of one that's closed as
duplicate. The fact that something is reported more than once appears
to be an indication that a bug/enhancement affects people more than
others. Agreed?
Can a person vote more than once on a ticket? Sounds a bit annoying if
that's possible.
In principle I agree, if we put that technical issue aside. It would be
nice to see more people voting on tickets in general. I think few
tickets have more than 3 votes currently so the list doesn't seem really
usable to priorize things.
And in general, I'd say devs are pretty busy with their own TODO list so
I don't know how much of an effect the availability of the votes will
make. But we can certainly add it to our "I don't know what to
contribute" page in addition to the easy tasks?
--
Adrien.
Other related posts:
