Re: [AD] 5.2 - What's needed?

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


It would be nice if there was some official roadmap or todo-list that was publicly accessible (but read-only to non-devs) so everyone interested could immediately see what is going on, what needs to be done, and where they could help out.

IMHO 5.2 is mainly stabilizing the new 5.1 parts of the API, as that is what needs to be maintained compatibility with later. SL's new approach to the "unstable" problem by marking individual functions as unstable in the future seems to be a very good idea. From what I remember from when I went through the docs, apart from video and joysticks, the audio recording API, the mouse emulation modes for touch input, and the native menus might possibly need another look. Maybe it was only the docs though.

I posted some lists with minor docs issues and very minor API naming inconsistencies here:
https://www.allegro.cc/forums/thread/615306	
https://www.allegro.cc/forums/thread/615183

By the way, please don't call it Allegro 6. ^^

Kind regards,
Polybios


On 2015-06-14 9:56 AM, Trent Gamblin wrote:
On 2015-06-14 1:50 AM, Trent Gamblin wrote:
On Jun 14, 2015 1:29 AM, Beoran <beoran@xxxxxxxxxx> wrote:
https://wiki.allegro.cc/index.php?title=Allegro_roadmap that should be
checked for inclusion after the 5.2.0 release.
I chuckled because it's obvious some users added whatever they want to the 5.2 roadmap. There's some stuff from Peter's email there and then some questionable stuff... Some of it is good though.


By the way, I think having a better roadmap is a good idea, but don't
put it on the Wiki. So far I think it should contain Peter's email from
ages ago and SiegeLord's recent email.

------------------------------------------------------------------------------





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