Frank-Rainer Grahl wrote on 8/05/2020 8:18 PM:
<Snip>
Basically only the browser works right in 2.57. Various problems with
the other components. Usually use it only when I encounter a web site
broken in 2.53 to check, when I find some time for a few 2.57 fixes or
test 2.53 to 2.57 ports.
FRG
Frank-Rainer, If you don't mind, what is the sequence used when
producing newer versions??
In my little bit I knowledge, I would have thought one version was
basically an improvement on the previous version, e.g.
1. Version ! of a program is produced and distributed.
2. Users of Version 1 find some problems with that version.
3. Version 2 includes some corrections (but code basically the same)
and released.
4. Users of Version 2 find some problems
5. Version 3 includes some corrections (but code basically the same)
and released.
etc, etc, etc.
Basically, once a version is "Out the door", all work on it ceases and
full resources are dedicated to production of the Newer, Improved
version. Well, O.K., maybe if there is a complete change of coding there
might be "Spill" version of the already "Out the door", 'current'
version, but nothing big!
With a small'ish workforce of Volunteers, I would think this model might
make best use of the limited resources! *IMHO* of course. ;-)
But what would I know?? ;-P Not much!
--
Daniel
Win7 User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0)
Gecko/20100101 SeaMonkey/2.49.5 Build identifier: 20190609032134
Linux User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0)
Gecko/20100101 SeaMonkey/2.49.1 Build identifier: 20171015235623
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
