Template talk:Current release

Download URLs

could/should this also be extended to directly provide URLs to download the latest binaries ? --Hooray (talk) 03:59, 4 September 2016 (EDT)

That sounds more like a job for a separate template that transcludes this one.

Bugman (talk) 14:51, 13 September 2016 (EDT)

also agreed, sounds like a much better idea - as long as the files are consistently named, we could then also link to the correct changelog automatically. --Hooray (talk) 15:03, 13 September 2016 (EDT)

Translations

I think it would be good to slightly extend this template to include the full 2016.3.1 number (maybe via a new parameter), and to include the full date translations via {{LangSwitch}}. Then the FlightGear page and its translations would never need updating for a new release.

Bugman (talk) 14:54, 13 September 2016 (EDT)

fully agreed - that is one of the reasons why the whole "LocalizedReleaseAnnouncement" (?) hack was originally introduced. --Hooray (talk) 15:03, 13 September 2016 (EDT)

Will not work properly

In its current state it will update the whole version-number (2016.4.1) on the 30th of every release-month (so Nov 30). We could change the round operator (floor) to round 0, but then it would update every 1st day in release month (now Feb 1st). But it has to update every release day: e.g. regular every 17th(see release plan) and if there are delays even later. Possible solutions:

1. Code the day 17 finaly for every release. Advantage: Don't have to care about it anymore. Disadvantage: no support for delayed release.
2. Write the dates and version numbers manually without any calculation (except the days until) and update them manualy as it was before. (you have to know when you have lost a fight) Advantage: works, even with delays and cancelled release!
3. Create a subtemplate including the date of the next release which has to be updated manualy. The template Current release here looks which version has to be released at given date to calculate the version (e.g. when the subtemplate date is 25 February 2017 it would calculate the version 2017.1 because it is close to 17 February 2017). Would be compartible for delays if they are not more than two months behind the plan. Disadvantage: one more template. But to write it into this template here is not an option as it is used 4 times and then even option 2. would be faster to update.

My favourite is 3. Skybike (talk) 17:55, 19 November 2016 (EST)

I think for now I'll put it back to manual. Its still reasonably easy and quick to update it. But maybe one day I'll try a more automated approach.

Red Leader (Talk, contribs) 07:27, 20 November 2016 (EST)