Re: [AD] Bug triage

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


I'd prefer to just keep them. With github's tag support, they don't really interfere, I think.

I'd be nice to relabel all the 4.9/5.0/5.1 bugs to something that doesn't involve a version though... perhaps 'A5'? I didn't explore if there are facilities to do mass relabelings like that.

-SL

On 08/26/2015 11:55 AM, Beoran wrote:
Today I spent sometime reading all the bugs that SiegeLord imported from
Sourceforge to Github, and I commented on some of them.
I was only able to close one bug because I saw it had been resolved by
studying the source code. My impression, though is that we should close
all bugs that refer to allegro 4.4 or lower, but keep the 4.9 and higher
ones that are still relevant. Does everyone agree with this approach?
Also if you have time , could all of you you check any bugs that you
reported yourself and see if they still apply, comment on them if they
do, or close them if they are already fixed?

Thanks in advance for your efforts!

Kind Regards,

B.




_______________________________________________
Allegro-developers mailing list
Allegro-developers@xxxxxxxxxx
https://mail.gna.org/listinfo/allegro-developers




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/