-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting ready for 0.4.3, outstanding issues #201
Comments
PING? |
@chrisisonwildcode PING |
I don't think we'll get any 'PONG's soon. I suggest that we release what we have and leave other stuff in limbo. |
OK, I'll give it until this weekend at the very latest. |
I made a draft-release for 0.4.3. If updates happen, I can happily refresh. |
Great, thanks. :) |
I think it is 'weekend enough' so I published the 0.4.3 release. |
Cheers! :) I'll see that it gets to Debian -> Ubuntu |
Still not there? |
Newp... i put out the email the interested party (bugged me for not fixing a bug). If they won't answer by tomorrow, I'll email someone else tomorrow who will likely respond in the next day. |
I think we have more than enough material for a new 0.4.3 release.
There are still issues that need solving. E.g.:
Wrong, very long duration detected for MIDI_0088.MID from Daggerfall
issue with MIDI_0088.MID and MIDI_0089.HMI from Daggerfall #176
impossibly long duration with crafted midi files:
impossibly long duration with crafted midi file #200 (might be related to issue with MIDI_0088.MID and MIDI_0089.HMI from Daggerfall #176)
more size checks needed in f_hmi.c, f_hmp.c, and possibly f_xmidi.c
more size checks needed in f_hmi.c, f_hmp.c, and possibly f_xmidi.c #189
And maybe this one (not really sure):
This song has some breaks #158
We can still make a 0.4.3 release and change milestone for the above
to 0.4.4. What do you think?
The text was updated successfully, but these errors were encountered: