[opensuse] Re: Beagle sucks
Andreas Jaeger
Check the plugin support for both, beagle contains more.
With openSUSE 11.0 beagle should be more resource friendly, where exactly do you still have problems?
Thanks for the info. I will test it out as soon as I upgrade to 11.0. I have a habit of not upgrading until there is a point release. Also like I said before I presonally use Mairix for mail, and Namazu in conjunction with namazu.el and a web frontend for everything else. Charles
Charles philip Chan escribió: I
have a habit of not upgrading until there is a point release.
is it some kind of esoteric Superstition about version numbers right ? :-D Let 's make it clear, release numbers means absolutely *nothing*, it is just marketing ;-P they have zero influence in product stability, features or whatever. -- "A computer is like an Old Testament god, with a lot of rules and no mercy. " Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
Charles philip Chan escribió: I
have a habit of not upgrading until there is a point release.
is it some kind of esoteric Superstition about version numbers right ? :-D
Let 's make it clear, release numbers means absolutely *nothing*, it is just marketing ;-P they have zero influence in product stability, features or whatever.
What world do you live in? Release numbers mean whatever the developers of a particular product make them mean, as a result of what they do or don't do to the product. And usually it means something fairly similar on almost every product, not just opensuse. A lot of stuff "just works" in opensuse10.3 that no longer works or is no longer as reliable in 11.0 Why? Because the decision-makers at suse adhere to the perfectly reasonable and common convention that certain classes of changes are avoided within a given release cycle or major version number, and many larger changes are saved up and allowed to happen only at the beginning of each new version. Thus X.0 almost always has a very significant meaning and impact. I have brand new machines that I have to ship out with 10.3 today because I have been unable to get 11.0 to install a working boot loader on them and I've been trying for weeks. 10.3 drops right in and works. 10.3 is the result of more testing and fixing than new feature additions or experimental improvements. 11.0, like any X.0 of any product, is the result of just the opposite, more new features and advancements than testing and fixing. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Brian K. White wrote:
Thus X.0 almost always has a very significant meaning and impact.
"impact" is where the misunderstanding seems to have been lately. "impact" in a major Linux distribution release should mean an increase in function that may, but does not always require, changes by the end user in configuration or setup to take advantage of new function or reliability. "impact" in a release should never mean "broken" or "dysfunctional" or a "decrease in reliability" (1) The determining factor between the two is a sufficient amount of time in the release cycle for adequate coding and quality assurance of new functionality to insure against a decrease in functionality. (2) The second most important factor is release dates driven by realistic estimates of time for incorporation of new functionality and quality assurance from the _actual_ _software_ _developers_ and not adherence to arbitrary schedules dictated by those without the competence or experience to contribute to the code. Anytime you see a release where impact means "broken" or "dysfunctional" or a "decrease in reliability", regardless of whether the release is (dot 0, dot 1, dot 2 or dot 3) there has been a failure at the decision making level to adhere to (1) and (2) above. On a lighter side: Have you ever wondered why you never see a "dot 4?" -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2008-08-15 at 18:54 -0500, David C. Rankin wrote:
Brian K. White wrote:
Thus X.0 almost always has a very significant meaning and impact.
"impact" is where the misunderstanding seems to have been lately.
"impact" in a major Linux distribution release should mean an increase in function that may, but does not always require, changes by the end user in configuration or setup to take advantage of new function or reliability.
"impact" in a release should never mean "broken" or "dysfunctional" or a "decrease in reliability"
I agree with you David, but as we all know, pretty much every build of any software & OS are going to have bugs. There were definite problems with 11.0, namely with some of the software included (*cough* Banshee not downloading podcasts *cough*), but overall it felt like a good experience. Anytime you do major updates to the either underlying or userland code, you're going to experience problems, we all know that. And no company/project, whether it's openSUSE & Novell, Red Hat, or Microsoft for that matter, can test their OS with every piece of hardware out on the market. So obviously problems do ensue occasionally.
(2) The second most important factor is release dates driven by realistic estimates of time for incorporation of new functionality and quality assurance from the _actual_ _software_ _developers_ and not adherence to arbitrary schedules dictated by those without the competence or experience to contribute to the code.
...and that's what we have. Who do you think is making the openSUSE
Roadmap? It's the core developers who know openSUSE inside and out
making the best decisions possible to release a good product.
--
Kevin "Yo" Dupuy - openSUSE Member
Public Mail:
participants (5)
-
Brian K. White -
Charles philip Chan -
Cristian Rodríguez -
David C. Rankin -
Kevin Dupuy