20,741
edits
Release plan: Difference between revisions
Jump to navigation
Jump to search
m
→2.10: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40179.html
m (→2.10) |
m (→2.10: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40179.html) |
||
| Line 200: | Line 200: | ||
This is a list of lessons learned from the previous releases, things that turned out well and should be kept for the next release as well as thing that didn't turn out so well and should be changed for future releases. Ideally, the release plan should be updated and augmented so that the lessons learned are incorporated accordingly. | This is a list of lessons learned from the previous releases, things that turned out well and should be kept for the next release as well as thing that didn't turn out so well and should be changed for future releases. Ideally, the release plan should be updated and augmented so that the lessons learned are incorporated accordingly. | ||
==== 2.12 ==== | |||
==== 2.10 ==== | ==== 2.10 ==== | ||
'''!!! NOTE: None of these issues have been incorporated into the release plan yet !!!''' | '''!!! NOTE: None of these issues have been incorporated into the release plan yet !!!''' | ||
| Line 208: | Line 209: | ||
** But it might be a good idea to create a script that will distribute the new builds to the various mirrors. That way I'm less likely to throttle the build server to 10k/sec [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39782.html] | ** But it might be a good idea to create a script that will distribute the new builds to the various mirrors. That way I'm less likely to throttle the build server to 10k/sec [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39782.html] | ||
** we could also automatically seed them in BitTorrent, on a Linux box and use "btmakemetafile" which I use here to generate those update packages on [http://mxchange.org:23456/ the tracker] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39783.html] | ** we could also automatically seed them in BitTorrent, on a Linux box and use "btmakemetafile" which I use here to generate those update packages on [http://mxchange.org:23456/ the tracker] [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39783.html] | ||
** perform a sync with JSBSim sources before the feature freeze. | ** perform a sync with JSBSim sources before the feature freeze [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40179.html]. | ||
** decide early on if/when navdata can be updated [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39280.html] | ** decide early on if/when navdata can be updated [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39280.html] | ||
** merge requests that didn't make it into the previous release should probably be handled early during the upcoming release cycle | ** merge requests that didn't make it into the previous release should probably be handled early during the upcoming release cycle | ||