Re: seamonkeyblog: End of an era… SeaMonkey’s old infrastructure.

2018-09-11 Thread GerardJan

EE wrote:

Daniel wrote:

Edmund Wong wrote on 11/09/2018 2:05 PM:

Ant wrote:

https://blog.seamonkey-project.org/2018/09/11/end-of-an-era/

Can't wait to see the future of SeaMonkey. I wonder if this means no
more minor v2.49.x releases with security fixes. :(


No, it just means that we'll release the v2.49.x when we get
this mess cleared up.  And by "mess", I mean the new infrastructure
which is unfortunately, taking a lot longer to get running
properly than I had anticipated.

Mainly because I'm also trying to incorporate the build config
changes to be able to build both comm-as-topsrcdir and moz-as-top.

I do apologize for the delay.

Edmund


Whenever you guys get around to it, Edmund, that will be fine!!

Make sure you guys have a life outside SeaMonkey!! ;-)


I do, at least.  I have Pale Moon as well!



an I have icecat, but i do not use it

--
https://facebook.com/gerardjan.vinkesteijn
Karl's version of Parkinson's Law:  Work expands to exceed the time alloted it.

Fedora20
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 
SeaMonkey/2.49.4

Build identifier: 20180711183816

ps. family: https://vinkesteijn.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: seamonkeyblog: End of an era… SeaMonkey’s old infrastructure.

2018-09-11 Thread GerardJan

Ant wrote:

On 9/10/2018 10:37 PM, Wolf wrote:

Edmund Wong schrieb:

Ant wrote:

https://blog.seamonkey-project.org/2018/09/11/end-of-an-era/

Can't wait to see the future of SeaMonkey. I wonder if this means no
more minor v2.49.x releases with security fixes. :(


No, it just means that we'll release the v2.49.x when we get
this mess cleared up.  And by "mess", I mean the new infrastructure
which is unfortunately, taking a lot longer to get running
properly than I had anticipated.

Mainly because I'm also trying to incorporate the build config
changes to be able to build both comm-as-topsrcdir and moz-as-top.

I do apologize for the delay.

Edmund


Wish you luck and please keep going!!!


Ditto! SM 4ever! :D


:P \:P


--
https://facebook.com/gerardjan.vinkesteijn
Karl's version of Parkinson's Law:  Work expands to exceed the time alloted it.

Fedora20
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 
SeaMonkey/2.49.4

Build identifier: 20180711183816

ps. family: https://vinkesteijn.com
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: seamonkeyblog: End of an era… SeaMonkey’s old infrastructure.

2018-09-11 Thread Ant via support-seamonkey

On 9/10/2018 10:37 PM, Wolf wrote:

Edmund Wong schrieb:

Ant wrote:

https://blog.seamonkey-project.org/2018/09/11/end-of-an-era/

Can't wait to see the future of SeaMonkey. I wonder if this means no
more minor v2.49.x releases with security fixes. :(


No, it just means that we'll release the v2.49.x when we get
this mess cleared up.  And by "mess", I mean the new infrastructure
which is unfortunately, taking a lot longer to get running
properly than I had anticipated.

Mainly because I'm also trying to incorporate the build config
changes to be able to build both comm-as-topsrcdir and moz-as-top.

I do apologize for the delay.

Edmund


Wish you luck and please keep going!!!


Ditto! SM 4ever! :D
--
Never forget (9/11)!
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\If crediting, then use Ant nickname and URL/link.
  / /\ /\ \Axe ANT from its address if e-mailing privately.
 | |o   o| | http://antfarm.ma.cx / http://antfarm.home.dhs.org
\ _ /
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: seamonkeyblog: End of an era… SeaMonkey’s old infrastructure.

2018-09-11 Thread Ant via support-seamonkey

On 9/11/2018 1:39 AM, Alex Beauroy wrote:

On 11/09/2018 06:05, Edmund Wong wrote:

Ant wrote:

https://blog.seamonkey-project.org/2018/09/11/end-of-an-era/

Can't wait to see the future of SeaMonkey. I wonder if this means no
more minor v2.49.x releases with security fixes. :(


No, it just means that we'll release the v2.49.x when we get
this mess cleared up.  And by "mess", I mean the new infrastructure
which is unfortunately, taking a lot longer to get running
properly than I had anticipated.

Mainly because I'm also trying to incorporate the build config
changes to be able to build both comm-as-topsrcdir and moz-as-top.

I do apologize for the delay.

Edmund


May our gratitude express all your virtues!!!
I'm and old user since Netscape Communicator & I'm delighted with 
SeaMonkey.

Your work is part of History.
Viva Mozilla!!


Ditto. I remember using Netscape since v2.x back in college! :O
--
Never forget (9/11)!
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\If crediting, then use Ant nickname and URL/link.
  / /\ /\ \Axe ANT from its address if e-mailing privately.
 | |o   o| | http://antfarm.ma.cx / http://antfarm.home.dhs.org
\ _ /
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: seamonkeyblog: End of an era… SeaMonkey’s old infrastructure.

2018-09-11 Thread EE

Daniel wrote:

Edmund Wong wrote on 11/09/2018 2:05 PM:

Ant wrote:

https://blog.seamonkey-project.org/2018/09/11/end-of-an-era/

Can't wait to see the future of SeaMonkey. I wonder if this means no
more minor v2.49.x releases with security fixes. :(


No, it just means that we'll release the v2.49.x when we get
this mess cleared up.  And by "mess", I mean the new infrastructure
which is unfortunately, taking a lot longer to get running
properly than I had anticipated.

Mainly because I'm also trying to incorporate the build config
changes to be able to build both comm-as-topsrcdir and moz-as-top.

I do apologize for the delay.

Edmund


Whenever you guys get around to it, Edmund, that will be fine!!

Make sure you guys have a life outside SeaMonkey!! ;-)


I do, at least.  I have Pale Moon as well!

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


Re: seamonkeyblog: End of an era… SeaMonkey’s old infrastructure.

2018-09-11 Thread Daniel

Edmund Wong wrote on 11/09/2018 2:05 PM:

Ant wrote:

https://blog.seamonkey-project.org/2018/09/11/end-of-an-era/

Can't wait to see the future of SeaMonkey. I wonder if this means no
more minor v2.49.x releases with security fixes. :(


No, it just means that we'll release the v2.49.x when we get
this mess cleared up.  And by "mess", I mean the new infrastructure
which is unfortunately, taking a lot longer to get running
properly than I had anticipated.

Mainly because I'm also trying to incorporate the build config
changes to be able to build both comm-as-topsrcdir and moz-as-top.

I do apologize for the delay.

Edmund


Whenever you guys get around to it, Edmund, that will be fine!!

Make sure you guys have a life outside SeaMonkey!! ;-)

--
Daniel

User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 
SeaMonkey/2.49.1 Build identifier: 20171016030418


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
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: seamonkeyblog: End of an era… SeaMonkey’s old infrastructure.

2018-09-11 Thread Alex Beauroy

On 11/09/2018 06:05, Edmund Wong wrote:

Ant wrote:

https://blog.seamonkey-project.org/2018/09/11/end-of-an-era/

Can't wait to see the future of SeaMonkey. I wonder if this means no
more minor v2.49.x releases with security fixes. :(


No, it just means that we'll release the v2.49.x when we get
this mess cleared up.  And by "mess", I mean the new infrastructure
which is unfortunately, taking a lot longer to get running
properly than I had anticipated.

Mainly because I'm also trying to incorporate the build config
changes to be able to build both comm-as-topsrcdir and moz-as-top.

I do apologize for the delay.

Edmund


May our gratitude express all your virtues!!!
I'm and old user since Netscape Communicator & I'm delighted with SeaMonkey.
Your work is part of History.
Viva Mozilla!!

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


Re: seamonkeyblog: End of an era… SeaMonkey’s old infrastructure.

2018-09-10 Thread Wolf

Edmund Wong schrieb:

Ant wrote:

https://blog.seamonkey-project.org/2018/09/11/end-of-an-era/

Can't wait to see the future of SeaMonkey. I wonder if this means no
more minor v2.49.x releases with security fixes. :(


No, it just means that we'll release the v2.49.x when we get
this mess cleared up.  And by "mess", I mean the new infrastructure
which is unfortunately, taking a lot longer to get running
properly than I had anticipated.

Mainly because I'm also trying to incorporate the build config
changes to be able to build both comm-as-topsrcdir and moz-as-top.

I do apologize for the delay.

Edmund


Wish you luck and please keep going!!!

Regards
Wolf
(*Seamonkey* addicted)

--
Linux Mint 18.3 Sylvia, MATE, 64-bit
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 
SeaMonkey/2.49.4

Lightning-5.4 -sm+tb
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: seamonkeyblog: End of an era… SeaMonkey’s old infrastructure.

2018-09-10 Thread Edmund Wong
Ant wrote:
> https://blog.seamonkey-project.org/2018/09/11/end-of-an-era/
> 
> Can't wait to see the future of SeaMonkey. I wonder if this means no
> more minor v2.49.x releases with security fixes. :(

No, it just means that we'll release the v2.49.x when we get
this mess cleared up.  And by "mess", I mean the new infrastructure
which is unfortunately, taking a lot longer to get running
properly than I had anticipated.

Mainly because I'm also trying to incorporate the build config
changes to be able to build both comm-as-topsrcdir and moz-as-top.

I do apologize for the delay.

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


seamonkeyblog: End of an era… SeaMonkey’s old infrastructure.

2018-09-10 Thread Ant via support-seamonkey

https://blog.seamonkey-project.org/2018/09/11/end-of-an-era/

Can't wait to see the future of SeaMonkey. I wonder if this means no 
more minor v2.49.x releases with security fixes. :(

--
"Ants live safely till they have gotten wings." --unknown
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\If crediting, then use Ant nickname and URL/link.
  / /\ /\ \Axe ANT from its address if e-mailing privately.
 | |o   o| | http://antfarm.ma.cx / http://antfarm.home.dhs.org
\ _ /
 ( )
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey