Release plan: Difference between revisions

Release plan (view source)

Revision as of 23:09, 21 August 2013

923 bytes added , 21 August 2013

→‎2.12: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40609.html

Hooray

Administrators

20,741

edits

@@ Line 215: / Line 215: @@
 {{cquote|<nowiki>could we generate a full installation RC package for testing?  It would make it easier for testers not familiar with Git to use it, and would be quite
 handy for people like myself who do their development on Linux, but have Windows systems available for testing but without the git infrastructure or the time to download the entire git fgdata repository.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40608.html|title=<nowiki>Re: [Flightgear-devel] 2.12 is branched</nowiki>|author=<nowiki>Stuart Buchanan</nowiki>|date=<nowiki>Wed, 21 Aug 2013 07:29:32 -0700</nowiki>}}</ref>|<nowiki>Stuart Buchanan</nowiki>}}
+{{cquote|<nowiki>Jenkins only does what it's told by the scripts (mostly in fgmeta besides the CMake files) - so we're still at the mercy of missing files in the
+installer description and so on - I didn't yet automate a 'smoke test'[1] on Jenkins, since that would mean keeping a clean environment to run test
+installs, and involve several expensive operations since we'd be launching the sim. That's all doable but requires VMs and more energy than I have. In general
+I've been hoping to get enough people using the nightly builds that an automated smoke-test would be unnecessary but that's probably optimistic</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40609.html|title=<nowiki>Re: [Flightgear-devel] 2.12 is branched</nowiki>|author=<nowiki>James Turner</nowiki>|date=<nowiki>Wed, 21 Aug 2013 07:52:59 -0700</nowiki>}}</ref>|<nowiki>James Turner</nowiki>}}
 <references/>