Hi, It's been a while since Wesnoth 1.12.2 and 1.13.1 were released, and some rather notable bug fixes have been committed in the meantime to both branches (however, see below for more information on master's status). I'm also soon going to commit a workaround for a particularly pesky memory access bug affecting some versions of either libvorbisfile or libogg and causing random crashes when a certain track is used as background music (e.g. in the lobby); as well as a fix for a potential (minor) security issue.
What do you think of string-freezing the 1.12 branch this Friday 5th and releasing Wesnoth 1.12.3 on June 12? Please note that this means anything that needs to be backported from master to 1.12 should be done by *this Friday* in order to prevent last-minute commits introducing regressions. *** As for Wesnoth 1.13.1, I'd greatly prefer to release it alongside 1.12.3 due to the aforementioned security bug fix. However, the situation on master right now is not too good due to several blockers found to affect Wesnoth 1.13.0 and current master, which have not been fixed yet: * https://gna.org/bugs/?23630 * https://gna.org/bugs/?23523 * https://gna.org/bugs/?23399 * https://gna.org/bugs/?23629 * https://gna.org/bugs/?23509 * https://gna.org/bugs/?23496 The last three in particular are suspected to be originated by last year's SP/MP code unification project done under GSoC by RiftWalker, who I tried to contact last Saturday and have yet to hear back from. After talking with gfgtdf about it on IRC, I believe that it might be worth keeping these code changes and applying any necessary fixes for the sake of improving MP campaign support, but it ultimately depends on whether people are willing to work on it before the eventual 1.13 feature freeze (which is probably not going to happen this year anyway). Reverting them is sure to cause more problems at this point and cost us some precious time and energy. So, to sum up the master branch situation, these bugs must be fixed before 1.13.1 can be released, barring another "#23440 situation" cropping up in the meantime. (I'd like to take this opportunity to remind you that only the 1.12 branch goes under string freeze for a week before a release, so you are free to commit string changes to master at any time before the release date.) -- Regards Ignacio R. Morelle <shadowm> _______________________________________________ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
