A4-to-A5 is still alive! I just pushed to it ;)

Some complex A4 project just needs to be used as the motivation to get the
whole thing working. I'd like to see http://timewarp.sourceforge.net/
working :)

On Thu, Aug 27, 2015 at 11:35 AM, Elias Pschernig <[email protected]>
wrote:

> On Wed, Aug 26, 2015 at 2:55 PM, Beoran <[email protected]> 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.
>
>
> Thanks!
>
>
>> 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
>
>
> I agree that we should close them, I've seen many other projects close
> bugs as "out of date" in similar situations, sometimes just because a bug
> is older than 5 or 10 years with no activity. I don't know if that means we
> should not re-add any A4 bugs in the (theoretical) case that someone
> reports one. We are still the official Allegro 4 project as well, even if
> it has almost no users and no developers left. So I's say yes, delete those
> really old bugs with no chance of getting fixed, but not sure what to do in
> case we get a new report or someone wants to re-open an issue. There has
> been changes to A4 even in this year apparently:
> https://github.com/liballeg/allegro5/commits/4.4
>
> Too bad the A4-to-A5 project never got very far, it kinda was a fun idea
> to keep the A4 API alive through that :)
>
>
> _______________________________________________
> Allegro-developers mailing list
> [email protected]
> https://mail.gna.org/listinfo/allegro-developers
>
>
_______________________________________________
Allegro-developers mailing list
[email protected]
https://mail.gna.org/listinfo/allegro-developers

Reply via email to