Edmund Wong wrote:
> Daniel wrote:
>> Ant wrote on 19/12/2018 12:13 PM:
>>> https://blog.seamonkey-project.org/2018/12/19/updating-everyone/
>> Thanks for the link, Ant.
>>
>> And EWong and Co, Thank you, Thank you, Thank you for all your past
>> efforts.
>>
>> As Alex said on the blog ...
>> Quote
>> I keep hope for this project, and trust the SeaMonkey team to find a
>> good way to continue it despite the many problems.
>> It’s hard nowadays for you all, and I’m sad that I don’t have the skills
>> to help you.
>>
>> If it’s necessary to keep SeaMonkey alive, take your time.
>> Hang in there…
>> End Quote
>>
>> My *only* complaint about SM is with the ever increasing sub-version
>> numbers, .48, .49, .53, .57, etc!! Can I suggest, if you do go with the
> To be honest, I"m also tired of the increasing version numbers.  It's
> silly and it's a relic from the rapid train release days.
>
> I've always preferred the ol'  small # increments.  i.e. 2.1a1, 2.1b1
> 2.1rc1, and finally 2.1 :)
>
> Unfortunately, we can't change it to, say 3.x as it represents something
> new and improved.  Of course, we can always change how we represent
> versions.  But that's for another discussion.
> Was going to say the same!
I, as an SM end user, don't like the version numbering scheme. Perhaps
the new version with the new engine (if it's possible to create) shall
be version 3.0, then comes bug fixing versions (3.0.1, 3.0.2, etc), as
was 9 or so years ago.
I really miss you Sea Monkey, you're really my savior.

> _______________________________________________
> support-seamonkey mailing list
> support-seamonkey@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-seamonkey

_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to