Paul B. Gallagher wrote:
JeffM wrote:
Hmmm. I've already used this analogy once today (elsewhere).
Sometimes it only takes ONE individual to affect a change:
http://google.com/search?tbs=dfn:1q=hung-jury
OK, so if I dedicate my life to making sure everyone knows that it's
Effect change, not
Jay Garcia wrote:
On 16.07.2011 22:15, JeffM wrote:
--- Original Message ---
Graham wrote:
I'm liking Seamonkey less and less
[Large amounts of text elided]
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release
JeffM wrote:
JeffM wrote:
Hmmm. I've already used this analogy once today (elsewhere).
Sometimes it only takes ONE individual to affect a change:
http://google.com/search?tbs=dfn:1q=hung-jury
Paul B. Gallagher wrote:
OK, so if I dedicate my life to making sure everyone knows
that it's Effect
On 11-07-19 9:57 PM, Paul B. Gallagher wrote:
Agreed, it's valuable. But it's incomplete, just as your testing was
incomplete until someone using a different-language version tried it.
Good example.
Code used in Firefox and Thunderbird have quite a bit of automated
testing. See
Rostyslaw Lewyckyj wrote:
JeffM wrote:
JeffM wrote:
Hmmm. I've already used this analogy once today (elsewhere).
Sometimes it only takes ONE individual to affect a change:
http://google.com/search?tbs=dfn:1q=hung-jury
Paul B. Gallagher wrote:
OK, so if I dedicate my life to making sure
Chris Ilias wrote:
On 11-07-19 9:57 PM, Paul B. Gallagher wrote:
Agreed, it's valuable. But it's incomplete, just as your testing was
incomplete until someone using a different-language version tried it.
Good example.
Code used in Firefox and Thunderbird have quite a bit of automated
Paul B. Gallagher wrote:
Rufus wrote:
Paul B. Gallagher wrote:
JeffM wrote:
Paul B. Gallagher wrote:
Inviting end users who are incapable of coding or testing
is an empty promise.
Describe more fully incapable of testing.
What I mean is that most end users can demo a program, play
Paul B. Gallagher wrote:
Inviting end users who are incapable of coding or testing
is an empty promise.
Describe more fully incapable of testing.
If the developers want to know what end users think,
they need to ask them before the code is carved in stone.
This overlooks the scratching an itch
JeffM wrote:
Paul B. Gallagher wrote:
Inviting end users who are incapable of coding or testing
is an empty promise.
Describe more fully incapable of testing.
What I mean is that most end users can demo a program, play around for a
bit, and generally satisfy themselves that it works for
Paul B. Gallagher wrote:
WLS wrote:
Some good sources of information on what is going on with releases.
Planet Mozilla
http://planet.mozilla.org/
Mozilla Wiki
https://wiki.mozilla.org/Main_Page
MozillaZine Forums in the Build sections.
http://forums.mozillazine.org/index.php
Thanks.
JeffM wrote:
Describe more fully incapable of testing.
Paul B. Gallagher wrote:
What I mean is that most end users can demo a program,
play around for a bit,
and generally satisfy themselves that it works for their favorite tasks.
That actually constitutes a lot of data points.
They might
Paul B. Gallagher wrote:
JeffM wrote:
Paul B. Gallagher wrote:
Inviting end users who are incapable of coding or testing
is an empty promise.
Describe more fully incapable of testing.
What I mean is that most end users can demo a program, play around for a
bit, and generally satisfy
What fish? I've been using SeaMonkey from the beginning, no fish for me.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
Paul B. Gallagher wrote:
The point of this discussion is that the vast majority of SeaMonkey
users (other than that very small élite who do contribute) find out
about feature changes far too late in the process to provide any useful
input. If the developers want to know what end users think,
Paul B. Gallagher wrote:
JeffM wrote:
Paul B. Gallagher wrote:
Inviting end users who are incapable of coding or testing
is an empty promise.
Describe more fully incapable of testing.
What I mean is that most end users can demo a program, play around for a
bit, and generally satisfy
Rufus wrote:
Paul B. Gallagher wrote:
JeffM wrote:
Paul B. Gallagher wrote:
Inviting end users who are incapable of coding or testing
is an empty promise.
Describe more fully incapable of testing.
What I mean is that most end users can demo a program, play around for a
bit, and generally
Justin Wood (Callek) wrote:
Paul B. Gallagher wrote:
JeffM wrote:
Paul B. Gallagher wrote:
Inviting end users who are incapable of coding or testing
is an empty promise.
Describe more fully incapable of testing.
What I mean is that most end users can demo a program, play around
for a
JeffM wrote:
Hmmm. I've already used this analogy once today (elsewhere).
Sometimes it only takes ONE individual to affect a change:
http://google.com/search?tbs=dfn:1q=hung-jury
Paul B. Gallagher wrote:
OK, so if I dedicate my life to making sure everyone knows
that it's Effect change, not
Interviewed by CNN on 19/07/2011 21:57, Joe32065 told the world:
What fish? I've been using SeaMonkey from the beginning, no fish for me.
http://www.amazon.com/So-Long-Thanks-All-Fish/dp/0345479963/ref=sr_1_1?s=booksie=UTF8qid=1311129552sr=1-1
--
MCBastos
This message has been protected
Rostyslaw Lewyckyj wrote:
JeffM wrote:
JeffM wrote:
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release Candidate trial/review process.
Jay Garcia wrote:
What else is required other than to be a user,
A critique
d...@kd4e.com wrote in message
news:mailman.2967.1310869475.4544.support-seamon...@lists.mozilla.org...
I think you may find Midori a superior choice to Chrome.
No spying and much tighter code.
I took a look but it requires Python 2.4, which I don't have, and am not
interested in installing.
Philip Chee wrote:
On 18/07/2011 12:50, Philip Chee wrote:
On 18/07/2011 10:46, Rostyslaw Lewyckyj wrote:
All right, then where does the developer council/
governing body publish the details of the planned
changes to be introduced in the next release, so that
interested users can make their
Paul B. Gallagher wrote:
Philip Chee wrote:
On 18/07/2011 12:50, Philip Chee wrote:
On 18/07/2011 10:46, Rostyslaw Lewyckyj wrote:
All right, then where does the developer council/
governing body publish the details of the planned
changes to be introduced in the next release, so that
On 07/18/2011 05:28 PM, Rostyslaw Lewyckyj wrote:
Paul B. Gallagher wrote:
...
If you're planning to move or take away our cheese, we still
don't know about it.
Succintly stated! :)
We, users, can not influence the product. All we can do is
offer our opinions after the fact and choose
Mon, 18 Jul 2011 18:25:47 -0700, /NoOp/:
On 07/18/2011 05:28 PM, Rostyslaw Lewyckyj wrote:
Paul B. Gallagher wrote:
...
If you're planning to move or take away our cheese, we still
don't know about it.
Succintly stated! :)
We, users, can not influence the product. All we can do is
offer
Stanimir Stamenkov wrote:
Mon, 18 Jul 2011 18:25:47 -0700, /NoOp/:
On 07/18/2011 05:28 PM, Rostyslaw Lewyckyj wrote:
Paul B. Gallagher wrote:
...
If you're planning to move or take away our cheese, we still
don't know about it.
Succintly stated! :)
We, users, can not influence the
WLS wrote:
Some good sources of information on what is going on with releases.
Planet Mozilla
http://planet.mozilla.org/
Mozilla Wiki
https://wiki.mozilla.org/Main_Page
MozillaZine Forums in the Build sections.
http://forums.mozillazine.org/index.php
Thanks. More than I can read at
NoOp wrote:
On 07/18/2011 05:28 PM, Rostyslaw Lewyckyj wrote:
Paul B. Gallagher wrote:
...
If you're planning to move or take away our cheese, we still
don't know about it.
Succinctly stated! :)
We, users, can not influence the product. All we can do is
offer our opinions after the fact
Justin Wood (Callek) ha scritto:
On 7/16/2011 10:05 PM, Graham wrote:
Once again, I thank the Mozilla and Seamonkey teams for all their
efforts: the web and all its browsers are much better for their efforts;
even IE has improved by leaps and bounds because of Firefox. I won't be
along for the
On 7/17/2011 4:24 AM, Francesco Presel wrote:
So since, if I've understood correctly, passing from SM 2.1 to 2.2 and
so on is like it was passing from 2.0.1 to 2.0.2, couldn't add-on
developers usually just put a generic 2.* max version, and still be sure
that their extension will work, just as
JeffM wrote:
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release Candidate trial/review process.
Jay Garcia wrote:
What else is required other than to be a user,
A critique that comes as late as so many of these do
could
JeffM wrote:
JeffM wrote:
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release Candidate trial/review process.
Jay Garcia wrote:
What else is required other than to be a user,
A critique that comes as late as so many
JeffM wrote:
those folks who are prone to complaining
*should* be the ones who point out shortcomings
**when something can more easily be done about those**
i.e. **early** aka **during pre-release**.
Paul B. Gallagher wrote:
If you want people to comment before something is finalized,
you have to
JeffM wrote:
Not complaining about the content; it's the *timing* that bugs me.
Michael Gordon wrote:
Don't be too harsh on these late posters.
Well, as long as they don't get *too* whiney.
Some of us will not upgrade
until most of the major bugs have been corrected.
...which is a choice
Justin Wood (Callek) wrote:
On 7/16/2011 10:05 PM, Graham wrote:
Once again, I thank the Mozilla and Seamonkey teams for all their
efforts: the web and all its browsers are much better for their efforts;
even IE has improved by leaps and bounds because of Firefox. I won't be
along for the ride,
JeffM wrote:
JeffM wrote:
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release Candidate trial/review process.
Jay Garcia wrote:
What else is required other than to be a user,
A critique that comes as late as so many
JeffM wrote:
those folks who are prone to complaining
*should* be the ones who point out shortcomings
**when something can more easily be done about those**
i.e. **early** aka **during pre-release**.
Rostyslaw Lewyckyj wrote:
All right , then where does the developer coouncil/
governing body
Rostyslaw Lewyckyj wrote:
JeffM wrote:
JeffM wrote:
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release Candidate trial/review process.
Jay Garcia wrote:
What else is required other than to be a user,
A critique
JeffM wrote:
JeffM wrote:
those folks who are prone to complaining
*should* be the ones who point out shortcomings
**when something can more easily be done about those**
i.e. **early** aka **during pre-release**.
Rostyslaw Lewyckyj wrote:
All right , then where does the developer coouncil/
On 18/07/2011 10:46, Rostyslaw Lewyckyj wrote:
JeffM wrote:
JeffM wrote:
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release Candidate trial/review process.
Jay Garcia wrote:
What else is required other than to be a
On 18/07/2011 12:50, Philip Chee wrote:
On 18/07/2011 10:46, Rostyslaw Lewyckyj wrote:
JeffM wrote:
JeffM wrote:
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release Candidate trial/review process.
Jay Garcia wrote:
JeffM wrote:
JeffM wrote:
those folks who are prone to complaining
*should* be the ones who point out shortcomings
**when something can more easily be done about those**
i.e. **early** aka **during pre-release**.
Rostyslaw Lewyckyj wrote:
All right , then where does the developer coouncil/
I've used the Mozilla suite from the Netscape days on OS/2. Right up
to the end of the Seamonkey 1.x series, it always did what I needed, and
I am truly grateful for all the effort that's been put into Mozilla, and
Seamonkey in particular. I've tried Firefox, and used it extensively at
work,
I think you may find Midori a superior choice to Chrome.
No spying and much tighter code.
So, I've switched to Chrome. I don't particularly like it, but I'm
liking Seamonkey less and less anyway. Chrome doesn't have all the
plugins I want, but it has most of them, and despite worries about
On 7/16/2011 10:05 PM, Graham wrote:
Once again, I thank the Mozilla and Seamonkey teams for all their
efforts: the web and all its browsers are much better for their efforts;
even IE has improved by leaps and bounds because of Firefox. I won't be
along for the ride, but I will keep an eye open,
Graham wrote:
I'm liking Seamonkey less and less
[Large amounts of text elided]
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release Candidate trial/review process.
___
Graham wrote:
I've used the Mozilla suite from the Netscape days on OS/2. Right up
to the end of the Seamonkey 1.x series, it always did what I needed, and
I am truly grateful for all the effort that's been put into Mozilla, and
Seamonkey in particular. I've tried Firefox, and used it
While I think some of the criticism is justified, I don't think the
predictions are correct.
Yes, the transition to the rapid-release train has been troublesome. Not
just here on Seamonkey, but in Firefox too. But that happened in large
part because extension developers are still getting used to
JeffM wrote:
Graham wrote:
I'm liking Seamonkey less and less
[Large amounts of text elided]
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release Candidate trial/review process.
Yup. -JW
On 16.07.2011 22:15, JeffM wrote:
--- Original Message ---
Graham wrote:
I'm liking Seamonkey less and less
[Large amounts of text elided]
Whenever I see these long diatribes about SeaMonkey,
I note that they never mention the authors' participation
in the Release Candidate trial/review
50 matches
Mail list logo