On Sat, Oct 30, 2010 at 05:22, Nick Coghlan <ncoghlan at gmail.com> wrote: > Ultimately, the frequency of releases comes down to the burden on the > release manager and the folks that build the binary installers. Any > given RM is usually only responsible for one or two branches, but the > same two people (Martin and Ronald) typically build the Windows and > Mac OS X binaries for all of them. So if you add 2.6 and 3.1 together, > as well as the releases for 2.7 and 3.2 development, I think you'll > find releases happening a lot more often than an average of 1 every 4 > months. Right, the effort of those people is obviously the limiting factor here. Automating builds sounds like a good step forward. What are the sticky bits here? Martin, Ronald, how much of the process is not automated, and why is automating hard? Cheers, Dirkjan
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4