Re: Seamonkey release?

2016-10-23 Thread bwitzed
On Thursday, September 8, 2016 at 7:31:32 PM UTC-7, Edmund Wong wrote: > Stephan Thiele wrote: > > Sorry if this is a stupid question, but I don't really understand why > > there still is no Seamonkey update after the 2.40 release in March, > > almost half a year ago. > > No. Not a stupid questio

Re: Seamonkey release?

2016-10-14 Thread sean . nathan
WaltS48 wrote: On 10/12/2016 01:38 AM, sean.nat...@invalid.knights.nee wrote: Stephan Thiele wrote: Sorry if this is a stupid question, but I don't really understand why there still is no Seamonkey update after the 2.40 release in March, almost half a year ago. I am quite confused that there a

Re: Seamonkey release?

2016-10-12 Thread WaltS48
On 10/12/2016 01:38 AM, sean.nat...@invalid.knights.nee wrote: Stephan Thiele wrote: Sorry if this is a stupid question, but I don't really understand why there still is no Seamonkey update after the 2.40 release in March, almost half a year ago. I am quite confused that there a nightlies with v

Re: Seamonkey release?

2016-10-11 Thread sean . nathan
Stephan Thiele wrote: Sorry if this is a stupid question, but I don't really understand why there still is no Seamonkey update after the 2.40 release in March, almost half a year ago. I am quite confused that there a nightlies with version numbers increasing to 2.48 while there is not even a beta

Re: Seamonkey release?

2016-09-13 Thread TCW
On Thu, 8 Sep 2016 20:18:59 +0200, Stephan Thiele <100.59...@germanynet.de> wrote: >Sorry if this is a stupid question, but I don't really understand why there >still is no Seamonkey update after the 2.40 release in March, almost half a >year ago. >I am quite confused that there a nightlies with

Re: Seamonkey release?

2016-09-12 Thread Stephan Thiele
Hi, Edmund, thanks a lot for your explanations. I think I understood it’s pretty much to do and it’s difficult enough to merely adapt the changes in basic codebase and infrastructure. Thank you for all the work that you as volunteers put into the project, and hope on .. Stephan ___

Re: Seamonkey release?

2016-09-11 Thread NoOp
On 9/9/2016 7:23 PM, Felix Miata wrote: > Frank-Rainer Grahl composed on 2016-09-10 00:03 (UTC+0200): > >> In the mean time if you need a new release grab 2.45 from Adrian if you >> are on Windows or Linux. His releases are build from the original >> sources and bug reports against them are accept

Re: Seamonkey release?

2016-09-11 Thread Stanimir Stamenkov
Sun, 11 Sep 2016 07:42:22 -0700 (PDT), 2beesquare: On Thursday, September 8, 2016 at 11:19:07 AM UTC-7, Stephan Thiele wrote: Sorry if this is a stupid question, but I don't really understand why there still is no Seamonkey update after the 2.40 release in March, almost half a year ago. [...]

Re: Seamonkey release?

2016-09-11 Thread 2beesquare
On Thursday, September 8, 2016 at 11:19:07 AM UTC-7, Stephan Thiele wrote: > Sorry if this is a stupid question, but I don't really understand why there > still is no Seamonkey update after the 2.40 release in March, almost half a > year ago. > I am quite confused that there a nightlies with vers

Re: Seamonkey release?

2016-09-11 Thread Frank-Rainer Grahl
Jupp at best gtk2 is a short time solution but I would still base the next 1-2 releases on it. I didn't follow gtk bugs but 3.21 als was a can of worms a few months ago. 3.22 is supposed to be out soon so this would need to work. On Sat, 10 Sep 2016 23:45:14 +0200, Adrian Kalla wrote: >>W dniu

Re: Seamonkey release?

2016-09-10 Thread Felix Miata
Adrian Kalla composed on 2016-09-10 23:45 (UTC+0200): GTK2 is a dead horse. GTK2 with Gecko is even more dead. I wouldn't waste any time to let it keep breathing. Just choose a decent GTK3-theme and all your problems will vanish. I never needed any theme but Modern with GTK1 or GTK2. Why shoul

Re: Seamonkey release?

2016-09-10 Thread Adrian Kalla
W dniu 09/10/2016 o 05:46 PM, »Q« pisze: >> Agreed but gtk3 itself is a pile of and at some point sticking to >> gtk2 will no longer work ... I use Linux only occasionally but I am >> quite sure this is/will become a problem for Firefox too. 2.45 was >> supposed to use gtk2. I will ask in the next

Re: Seamonkey release?

2016-09-10 Thread »Q«
In , Frank-Rainer Grahl wrote: > Felix Miata wrote: > > Frank-Rainer Grahl composed on 2016-09-10 00:03 (UTC+0200): > > > >> In the mean time if you need a new release grab 2.45 from Adrian > >> if you are on Windows or Linux. His releases are

Re: Seamonkey release?

2016-09-10 Thread Frank-Rainer Grahl
WaltS48 wrote: Agreed but gtk3 itself is a pile of and at some point sticking to gtk2 will no longer work ... I use Linux only occasionally but I am quite sure this is/will become a problem for Firefox too. 2.45 was supposed to use gtk2. I will ask in the next status meeting if we should switch

Re: Seamonkey release?

2016-09-10 Thread WaltS48
On 09/10/2016 04:16 AM, Frank-Rainer Grahl wrote: Felix Miata wrote: Frank-Rainer Grahl composed on 2016-09-10 00:03 (UTC+0200): In the mean time if you need a new release grab 2.45 from Adrian if you are on Windows or Linux. His releases are build from the original sources and bug reports aga

Re: Seamonkey release?

2016-09-10 Thread Frank-Rainer Grahl
Felix Miata wrote: Frank-Rainer Grahl composed on 2016-09-10 00:03 (UTC+0200): In the mean time if you need a new release grab 2.45 from Adrian if you are on Windows or Linux. His releases are build from the original sources and bug reports against them are accepted: Last I tried a version ne

Re: Seamonkey release?

2016-09-10 Thread Frank-Rainer Grahl
Ray_Net wrote: Therefore the guy who say that WebMasters should sniff Gecko instead of other part of the Use Agent string are WRONG ! :-) No it just means that building Seamonkey is not possible for a time until the incompatibility is fixed. This is usually the case when you don't see any Nig

Re: Seamonkey release?

2016-09-09 Thread Felix Miata
Frank-Rainer Grahl composed on 2016-09-10 00:03 (UTC+0200): In the mean time if you need a new release grab 2.45 from Adrian if you are on Windows or Linux. His releases are build from the original sources and bug reports against them are accepted: Last I tried a version newer than 2.42 I foun

Re: Seamonkey release?

2016-09-09 Thread Ed
On 09/09/16 6:03 PM, Frank-Rainer Grahl wrote: > Felix Miata wrote: >> WaltS48 composed on 2016-09-09 09:22 (UTC-0400): >> >>> I think the SeaMonkey developers should base the next version on Gecko >>> 45 ESR (which would have been SM 2.42), call it SM 2.45 and bring it up >>> to date with the Fire

Re: Seamonkey release?

2016-09-09 Thread Ray_Net
Paul Bergsagel wrote on 09/09/2016 02:43: Some of the changes to Gecko are not compatible with Seamonkey. Our Seamonkey programmers do amazing work adapting/reverting Gecko changes made by FireFox programmers so that Seamonky and NOT some offshoot clone of Firefox.I praise the SeaMonkey progra

Re: Seamonkey release?

2016-09-09 Thread Frank-Rainer Grahl
Felix Miata wrote: WaltS48 composed on 2016-09-09 09:22 (UTC-0400): I think the SeaMonkey developers should base the next version on Gecko 45 ESR (which would have been SM 2.42), call it SM 2.45 and bring it up to date with the Firefox ESR security and stability releases. I think that would mak

Re: Seamonkey release?

2016-09-09 Thread EE
Edmund Wong wrote: Stephan Thiele wrote: Sorry if this is a stupid question, but I don't really understand why there still is no Seamonkey update after the 2.40 release in March, almost half a year ago. No. Not a stupid question at all. In fact, it's a very good question. I am quite confus

Re: Seamonkey release?

2016-09-09 Thread Felix Miata
WaltS48 composed on 2016-09-09 09:22 (UTC-0400): I think the SeaMonkey developers should base the next version on Gecko 45 ESR (which would have been SM 2.42), call it SM 2.45 and bring it up to date with the Firefox ESR security and stability releases. I think that would make it currently SM 2.

Re: Seamonkey release?

2016-09-09 Thread WaltS48
On 09/09/2016 03:01 AM, Edmund Wong wrote: Edmund, A good explanation. So, here's my question: Are there any Gecko alternatives out there that aren't changing at a such a furious rate? Something to give us a reasonable (and safe) SM but perhaps with a more consistent internal interface that wou

Re: Seamonkey release?

2016-09-09 Thread cmcadams
Edmund Wong wrote: Edmund, A good explanation. So, here's my question: Are there any Gecko alternatives out there that aren't changing at a such a furious rate? Something to give us a reasonable (and safe) SM but perhaps with a more consistent internal interface that would be simpler to integr

Re: Seamonkey release?

2016-09-09 Thread Edmund Wong
> > Edmund, > > A good explanation. > > So, here's my question: Are there any Gecko alternatives out there that > aren't changing at a such a furious rate? Something to give us a > reasonable (and safe) SM but perhaps with a more consistent internal > interface that would be simpler to integrate

Re: Seamonkey release?

2016-09-08 Thread cmcadams
Edmund Wong wrote: Stephan Thiele wrote: Sorry if this is a stupid question, but I don't really understand why there still is no Seamonkey update after the 2.40 release in March, almost half a year ago. No. Not a stupid question at all. In fact, it's a very good question. I am quite confus

Re: Seamonkey release?

2016-09-08 Thread Edmund Wong
Stephan Thiele wrote: > Sorry if this is a stupid question, but I don't really understand why > there still is no Seamonkey update after the 2.40 release in March, > almost half a year ago. No. Not a stupid question at all. In fact, it's a very good question. > I am quite confused that there a

Re: Seamonkey release?

2016-09-08 Thread Paul Bergsagel
Stephan Thiele wrote: Sorry if this is a stupid question, but I don't really understand why there still is no Seamonkey update after the 2.40 release in March, almost half a year ago. I am quite confused that there a nightlies with version numbers increasing to 2.48 while there is not even a beta

Re: SeaMonkey Release Delay(s)

2014-08-05 Thread EE
hawker wrote: On 7/16/2014 9:07 PM, Justin Wood (Callek) wrote: Hey Everyone, Again I'm sorry for delays on beta's, and sorry for delays which caused us to technically skip a gecko release last cycle. But I wanted to give you all a followup, I'm getting much closer to getting a beta out there

Re: SeaMonkey Release Delay(s)

2014-07-31 Thread Ant
Cool and thanks. :) On 7/30/2014 9:10 PM PT, Justin Wood (Callek) typed: Just an update everyone, The physical machines are in place and "good" I'm working on getting the buildbot (automation) up to snuff with :ewong's help to make use of this. ~Justin Wood (Callek) On 7/16/2014 9:07 PM, Ju

Re: SeaMonkey Release Delay(s)

2014-07-30 Thread Justin Wood (Callek)
Just an update everyone, The physical machines are in place and "good" I'm working on getting the buildbot (automation) up to snuff with :ewong's help to make use of this. ~Justin Wood (Callek) On 7/16/2014 9:07 PM, Justin Wood (Callek) wrote: Hey Everyone, Again I'm sorry for delays on bet

Re: SeaMonkey Release Delay(s)

2014-07-29 Thread Ant
Any status update on SM's delay? ;) -- "He who cannot pick up an ant, and wants to pick up an elephant will some day see his folly." --African /\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site) / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net | |o o

Re: SeaMonkey Release Delay(s)

2014-07-22 Thread MCBastos
Interviewed by CNN on 21/07/2014 01:28, Justin Wood (Callek) told the world: > For the record, I couldn't have said this better myself. > > (I probably have attempted to many times in the past though) > > Thank you MCBastos. I'm happy to give what little help I'm able to contribute. Feel free to

Re: SeaMonkey Release Delay(s)

2014-07-21 Thread bdelmee
Cheers Justin (and all devs) for a continued, albeit mostly thankless job. And thanks MCBastos for a clear explanation of why sticking to ESR releases is not the panacea it might appear to be. If I am not mistaken,the debian devs tried just that for their squeeze package of seamonkey (aka iceape),

Re: SeaMonkey Release Delay(s)

2014-07-20 Thread Justin Wood (Callek)
For the record, I couldn't have said this better myself. (I probably have attempted to many times in the past though) Thank you MCBastos. ~Justin Wood (Callek) SeaMonkey Council Member SeaMonkey Release Engineer On 7/18/2014 1:39 AM, MCBastos wrote: Interviewed by CNN on 17/07/2014 16:18, haw

Re: SeaMonkey Release Delay(s)

2014-07-19 Thread Ant
On 7/19/2014 5:35 AM PT, arnel...@gmail.com typed: >> For a free application that has a much better user interface than Firefox, I refuse to complain that my current version is a month old. Ditto to that! Don't worry Justin, take the time you need to release next version. Yeah, we don't wa

Re: SeaMonkey Release Delay(s)

2014-07-19 Thread arnelnd1
Den torsdagen den 17:e juli 2014 kl. 17:25:32 UTC+2 skrev David E. Ross: > On 7/16/2014 6:07 PM, Justin Wood (Callek) wrote: > > > Hey Everyone, > > > > > > Again I'm sorry for delays on beta's, and sorry for delays which caused > > > us to technically skip a gecko release last cycle. > > >

Re: SeaMonkey Release Delay(s)

2014-07-17 Thread MCBastos
Interviewed by CNN on 17/07/2014 16:18, hawker told the world: > Why does SM have to stay on such a fast release schedule? What was wrong > with the slower schedule of yesteryear? Just because FF and TB do it > does SM need to as well? Sorta. The Firefox people are the ones responsible for Geck

Re: SeaMonkey Release Delay(s)

2014-07-17 Thread Danny Kile
hawker wrote: On 7/16/2014 9:07 PM, Justin Wood (Callek) wrote: Hey Everyone, Again I'm sorry for delays on beta's, and sorry for delays which caused us to technically skip a gecko release last cycle. But I wanted to give you all a followup, I'm getting much closer to getting a beta out there

Re: SeaMonkey Release Delay(s)

2014-07-17 Thread Trane Francks
On 7/18/14 4:18 AM, hawker wrote: Why does SM have to stay on such a fast release schedule? What was wrong with the slower schedule of yesteryear? Just because FF and TB do it does SM need to as well? The most important element there is to stay on top of security fixes. As vulnerabilities are

Re: SeaMonkey Release Delay(s)

2014-07-17 Thread Ray_Net
hawker wrote, On 17/07/2014 21:18: On 7/16/2014 9:07 PM, Justin Wood (Callek) wrote: Hey Everyone, Again I'm sorry for delays on beta's, and sorry for delays which caused us to technically skip a gecko release last cycle. But I wanted to give you all a followup, I'm getting much closer to gett

Re: SeaMonkey Release Delay(s)

2014-07-17 Thread hawker
On 7/16/2014 9:07 PM, Justin Wood (Callek) wrote: Hey Everyone, Again I'm sorry for delays on beta's, and sorry for delays which caused us to technically skip a gecko release last cycle. But I wanted to give you all a followup, I'm getting much closer to getting a beta out there now, and correc

Re: SeaMonkey Release Delay(s)

2014-07-17 Thread Ed Mullen
Justin Wood (Callek) pounded out : Hey Everyone, Again I'm sorry for delays on beta's, and sorry for delays which caused us to technically skip a gecko release last cycle. But I wanted to give you all a followup, I'm getting much closer to getting a beta out there now, and correcting dev versio

Re: SeaMonkey Release Delay(s)

2014-07-17 Thread David E. Ross
On 7/16/2014 6:07 PM, Justin Wood (Callek) wrote: > Hey Everyone, > > Again I'm sorry for delays on beta's, and sorry for delays which caused > us to technically skip a gecko release last cycle. > > But I wanted to give you all a followup, I'm getting much closer to > getting a beta out there n

Re: SeaMonkey Release Delay(s)

2014-07-17 Thread Ant
On 7/16/2014 10:30 PM PT, Daniel typed: ... ~Justin Wood (Callek) Thanks for your efforts with this update, Calleck. Any news on a Linux x64 Beta build, or is this somewhere further down the line?? Ditto. We still <3 SM even if they are a little old. :) -- "Oh, look what Kyle got me, it's a

Re: SeaMonkey Release Delay(s)

2014-07-16 Thread Daniel
On 17/07/14 11:07, Justin Wood (Callek) wrote: Hey Everyone, Again I'm sorry for delays on beta's, and sorry for delays which caused us to technically skip a gecko release last cycle. But I wanted to give you all a followup, I'm getting much closer to getting a beta out there now, and correctin