Talk:Release plan

From FlightGear wiki
Revision as of 12:52, 4 September 2012 by Fredb (talk | contribs)
Jump to navigation Jump to search

For the benefit of the unwashed masses...

Would it be acceptable to discuss this proposition on this page? I've never managed to use the dev list properly - it always ends up being rather messy. -- Armchair Ace 15:00, 23 May 2011 (EDT)

What about inserting in this cycle a refactory release?

Hi, I was thinking: wouldn't it sound gound to add a 'refactoring'/performance/bugfixing specific release in this cycle. Maybe use a 3.1 number for instance. This would enable devs and fellow contributors to focus on fixing bugs reported, and try to make performance better on their projects. -- f-ojac 09:33, 21 August 2012 (EDT)

Well, I like the idea, but I think it cannot be handled right now - due to the required workload for each release, just look at how people and resources are still the limiting factor here, even with "just 2" releases per year. This is because of all the manual work that's involved here. I don't think we'll see more releases without some serious automation work, like mentioned at Release plan#Open_items.2C_questions. Only after the release process is largely automated, can we expect more releases. Also, it's worth noting that, strictly speaking, refactoring is very different from improving performance or bugfixing. Bug fixing in particular is meant to be done during the code freeze period already. But, refactoring is all about keeping the existing behavior, while improving the design and the architecture to make it more maintainable. Now, having a "performance" release would be cool for a number of reasons,and FG can really be a resource hog. And FG eating up 14+ gb of RAM is just ridiculous and could have an impact on the project's reputation.--Hooray 04:42, 21 August 2012 (EDT)

FGRun inclusion

fgrun is now hosted in the fg project, and appears as a submodule of fgmeta in the master branch. A Jenkins task, Windows-rel-test, is configured to demonstrated the feasibility of including it in the final build process. What about including it in the release plan (same for maclauncher btw) ? -- Fredb 08:52, 4 September 2012 (EDT)