Hello,

As you might have noticed form IRC, Aginor is currently working on ironing 
some remaining issues with Wesnoth on SDL 2, in the sdl2 branch of the 
mainline repository.

Our hope is that once all top-priority SDL 2-specific bugs are fixed, the 
branch will be merged into mainline master and we'll have one or two weeks of 
testing on all platforms by developers. Then, 1.13.2 will be released to the 
public using SDL 2 by default, which means that to use SDL 1.2 with 1.13.2 
people will have to explicitly choose to do this with the CMake and SCons 
recipes, or download alternative SDL 1.2-based binaries for Windows and Apple 
OS X which our packagers may or may not decide to provide.

In the meantime, and in order to ease the merging step for us, I would like to 
request the following from you:

 1) All low-level code dealing with direct SDL* API calls should be considered 
*frozen* in master, meaning that no changes should be made to it unless it's 
strictly necessary to fix an important or blocker bug.

 2) The interfaces and implementation of hotkey management, GUI1 event 
handling, GUI2 event handling, image cache (including image path functions), 
clipboard support, and rendering engine (display, game_display and 
editor_display) should be considered *frozen* as well, to avoid surprises 
throughout the process.

If in doubt about whether a change may conflict with Aginor's work, just ask 
him (or me) about it. You are free to work on this kind of thing in parallel 
in your own forks, but you take full responsibility for dealing with any 
conflicts that might crop up at the end.

If everything goes well, master should be back to regular business in a month 
or two, and then we'll have version 1.13.2 running on SDL 2 in order to gauge 
the results stability and performance-wise among our user base at large. SDL 
1.2 support will then be removed in a subsequent development release, most 
likely 1.13.3.

Do also note that I may choose to release version 1.13.2 in the interim 
without the SDL 2 transition changes *iff* new security vulnerabilities are 
found. If it comes to that, all the provisions above should be considered to 
apply for 1.13.3 and 1.13.4 instead.

-- 
Regards
  Ignacio R. Morelle <shadowm>

_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev

Reply via email to