Replies: 4 comments 1 reply
-
Also, not all performance work has to be merged in the initial release, only correctness really matters. Performance improvements in subsequent releases make for great subsequent release announcements, driving more users to the library. |
Beta Was this translation helpful? Give feedback.
-
And finally I feel like I need to explain the end goals, i.e why it is like this and why are these changes not in image-rs, because I know someone will ask. Other than that I feel like you can write the release announcements, I'll write 2-3 blogs with some notes, why's and end goals and we can start the release. I can't give a real timeline, this is just a side project so I can't say exactly when |
Beta Was this translation helpful? Give feedback.
-
Update I think jpeg is almost done, I hope I haven't spoken too soon. PNG has that issue at #84 that I'm looking at, some images are animated hence why we have problems while others are genuine bugs in the decoder, but it should not be too long for it to be correct. Lower bit depths I'm still thinking about it. |
Beta Was this translation helpful? Give feedback.
-
Indeed, JPEG seems to be done. I'm going to do one last fuzzing pass and then share the fuzzing seeds. The preliminary fuzzing results are good. |
Beta Was this translation helpful? Give feedback.
-
How would you like to go about announcing the project?
I think announcing PNG and JPEG separately as soon as they're ready could be beneficial. Mostly because the PNG decoder would make for a great headline, and separate announcements usually drive more clicks. But you could also announce
zune-image
as a whole once it's ready, if you prefer.I can help write effective release announcements. I have been doing plenty of that, here's an example.
Beta Was this translation helpful? Give feedback.
All reactions