Well since we haven't begun work on a 7.2 release, everything committed since 7.0.28 is technically a bug fix.
Even the app_config.xml configuration file (http://boinc.berkeley.edu/trac/wiki/ClientAppConfig) started its life as a power user bug fix. Ideally, at some point in time, we can figure out a sane set of policies that the client/server can use to implement that functionality automatically. I recognize Steffen, Gianfranco, and all the Linux package maintainers have a really hard job. They are constantly trying to balance BOINC project goals with the Linux distro policies. From my perspective any build in the 7.0b branch past 7.0.28 should be able to be considered stable from a package maintainers perspective. Do I need to change something to better support our Linux package maintainers? ----- Rom -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Toralf Förster Sent: Tuesday, February 26, 2013 12:36 PM To: [email protected] Subject: Re: [boinc_alpha] Boinc alpha and the testing future (patchincluded) Probably Steffen compares the current BOINC version history + release management with the one of the linux kernel development model (which I like too). Said that, he's expecting (and I'd appreciate that too) that 7.0.x is just a bug fix version of 7.0.(x-1) rather than a feature-added version, right ? -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 _______________________________________________ boinc_alpha mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
