Board index FlightGear The FlightGear project

Release Plan: A Modest Proposal.

Questions about the FlightGear organisation, website, wiki etc.

Release Plan: A Modest Proposal.

Postby MIG29pilot » Wed Nov 18, 2015 2:37 pm

Lately there seems to have been some trouble with the release of FlightGear 3.6, and some talk of release plan optimization. I have an modest proposal to make. Suppose FlightGear, like warthunder, instead of making certain versions, made the official version somewhat like a git version; and that there would be a master release branch from which the user's copy would automatically pull every so often. The changes from the dev brach, once considered sable enough for the public, would then be pushed to this. The "Old versions" could be snapshots taken of the master branch taken periodically, say every six months. The user would also be able to disable these automatic updates if he or she wished. The advantages of this would be:
A.) New features, bug fixes, and other improvements would automatically be available for users;
B.) Those unfamiliar with Git could still automatically have changes delivered and installed;, without having to uninstall and reinstall (a time consuming and sometimes confusing process)
C.) No complex release plan.
User avatar
Posts: 1463
Joined: Tue May 19, 2015 4:03 pm
Location: 6 feet under Snow
Callsign: MIG29pilot
Version: 3.7nightly
OS: Windows 10

Re: Release Plan: A Modest Proposal.

Postby Hooray » Wed Nov 18, 2015 2:40 pm

Please don't send support requests by PM, instead post your questions on the forum so that all users can contribute and benefit
Thanks & all the best,
Help write next month's newsletter !
pui2canvas | MapStructure | Canvas Development | Programming resources
Posts: 11728
Joined: Tue Mar 25, 2008 8:40 am

Return to The FlightGear project

Who is online

Users browsing this forum: No registered users and 4 guests