20,741
edits
Release plan: Difference between revisions
→2.10
(→2.10) |
(→2.10) |
||
| Line 199: | Line 199: | ||
** {{Thumbs up}} It is great news if you are able to crank out full installers right from Jenkins. That will save me a bunch of downloading and hours of uploading for every new release candidate [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39781.html]. | ** {{Thumbs up}} It is great news if you are able to crank out full installers right from Jenkins. That will save me a bunch of downloading and hours of uploading for every new release candidate [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39781.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] | ** 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] | |||
** perform a sync with JSBSim sources before the feature freeze. | ** perform a sync with JSBSim sources before the feature freeze. | ||
** 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] | ||