Difference between revisions of "1.15 Roadmap"

From The Battle for Wesnoth Wiki
(1.15.10)
(1.15.9)
Line 31: Line 31:
  
 
== 1.15.9 ==
 
== 1.15.9 ==
* Add a <nowiki>forum_auth=yes|no</nowiki> attribute to _server.pbl to allow authenticating via the add-on author's forum username and password. Add-on authors utilizing this then wouldn't need to provide a separate author, email, or passphrase value, and would be more secure by not needing to store the passphrase for these add-ons in plaintext.
+
* Add a <nowiki>forum_auth=yes|no</nowiki> attribute to _server.pbl to allow authenticating via the add-on author's forum username and password. Add-on authors utilizing this then wouldn't need to provide a separate author, email, or passphrase value, and would be more secure by not needing to store the passphrase for these add-ons in plaintext (Pentarctagon)
  
 
== 1.15.10 ==
 
== 1.15.10 ==

Revision as of 18:13, 19 July 2020

This page is for consolidating and planning when new features and fixes are intended to land in the 1.15 development branch. The release schedule for Development releases can be found here. A thread for discussing this roadmap can also be found here. As a reminder, there is also the previous 1.16 Checklist issue on github, for those who added items to that.

Instructions

Place the feature or fix you intend to implement within the section of the point release that you intend to have it implemented by, as well as your forum username in parenthesis after the feature description. The point release something is planned to be released with is not set in stone, and can be updated as needed depending on the circumstances.

Additionally, the current set of 1.15 point releases is not final, and can be increased or decreased based on what features and fixes are planned. The only hard deadline, which hopefully is not an issue, is to have 1.16 released by February 2022. This will allow 1.16 to be in the Ubuntu 22.04 LTS release's repositories, and while I realize we don't plan Wesnoth's releases around any distro's schedule, there are also currently no other criteria to use as a final deadline and February 2022 is easily more than enough time to plan out and implement 1.16, especially given how long 1.14/1.15 have already been going.

1.15.4

  • Mainlining World conquest II (gfgtdf)
  • Have #4884 merged, as a lot of the rest of what I want to do depends on this (Pentarctagon)
  • add the logger level statements needed to fix #4898 (Pentarctagon)

1.15.5

  • Campaignd support for different min wesnoth versions (gfgtdf)

1.15.6

  • Api to query abilities and traits by id, whcih are then uses by the {TRAIT...}, {ABILITY...} macros (gfgtdf)
  • Re-add the dunefolk faction to WCII (gfgtdf)
  • Create the queryd program. Its purpose would be to execute SQL separate from wesnothd, so that queries that could potentially take several seconds or longer to complete won't block wesnothd from continuing to run until the query completes (Pentarctagon)
  • Implement a game history viewer by utilizing queryd (Pentarctagon)

1.15.7

  • Implement an MP reporting dialog as a replacement for the /query report <message> command that's available now. This could include functionality such as searching for the username(s) to report, searching for a particular game to report (currently running or already ended, if already ended then automatically include a link to the game's replay), and inserting a PM to the MP Moderators group from the reporter (though I'm not sure if this part is actually possible) (Pentarctagon)

1.15.8

  • Add SQL support to campaignd using mariadbpp (Pentarctagon)
  • Store add-on upload history in the database (Pentarctagon)

1.15.9

  • Add a forum_auth=yes|no attribute to _server.pbl to allow authenticating via the add-on author's forum username and password. Add-on authors utilizing this then wouldn't need to provide a separate author, email, or passphrase value, and would be more secure by not needing to store the passphrase for these add-ons in plaintext (Pentarctagon)

1.15.10

  • Have the Travis-CI MP unit tests validate database functionality as well. (Pentarctagon)

1.15.11

  • Remove the scenario editor functionality, keeping specific features that are useful, such as being able to place unit sprites (Pentarctagon)

1.15.12

1.15.13

1.15.14

1.15.15