"Re: Future releases"

2017-10-10 Thread Ant via support-seamonkey

https://blog.seamonkey-project.org/2017/10/11/re-future-releases/
--
"The ant has made him(here!)self illustrious; Through constant industry 
industrious.; So what? Would you be calm and placid; If you were full of 
formic acid?" --Ogden Nash (The Ant)
Note: A fixed width font (Courier, Monospace, etc.) is required to see 
this signature correctly.

   /\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
  / /\ /\ \Ant's Quality Foraged Links: http://aqfl.net
 | |o   o| |
\ _ /If crediting, then use Ant nickname and AQFL URL/link.
 ( )   Axe ANT from its address if e-mailing privately.
___
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey


Re: router login - error 401, unauthorized

2017-10-10 Thread Mason83
On 10/10/2017 08:38, Frank-Rainer Grahl wrote:

> You can update Adrians build to the official candidate 3:
> 
> https://ftp.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build3/
> 
> Should behave way better than the May build I hope :)
> 
> .1 because Adrian built 2.49 from the comm-release branch and we wanted 
> to distinguish it from this one. All 2.49.1 ones are build from the 
> esr52 branch.

I'm confused. Adrian's build shows up as
SeaMonkey version 2.49.1
You are currently on the esr update channel.
User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.1

So using .1 does not distinguish the official build from
Adrian's ESR-based builds.

> 2.49.1 is at current esr52.4 level. The next release will 
> be .2 Hopefully when 52.5 arrives but depends on how long it takes to 
> bake a release and how much time ewong has. In any case there will be a 
> .2 at a future 52.x esr level.

Thanks for that info.

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


Re: router login - error 401, unauthorized

2017-10-10 Thread Frank-Rainer Grahl

You can update Adrians build to the official candidate 3:

https://ftp.mozilla.org/pub/seamonkey/candidates/2.49.1-candidates/build3/

Should behave way better than the May build I hope :)

.1 because Adrian built 2.49 from the comm-release branch and we wanted 
to distinguish it from this one. All 2.49.1 ones are build from the 
esr52 branch. 2.49.1 is at current esr52.4 level. The next release will 
be .2 Hopefully when 52.5 arrives but depends on how long it takes to 
bake a release and how much time ewong has. In any case there will be a 
.2 at a future 52.x esr level.


FRG

Mason83 wrote:

On 08/10/2017 18:44, Frank-Rainer Grahl wrote:


Likely point 3 in the known issues in the 2.48 release notes:

https://www.seamonkey-project.org/releases/seamonkey2.48/

Fix will be in 2.49.1.

Maybe we should just drop the release notes and tell everyone to open a
lenghty thread in one of the support groups if he7she/it runs into a known
problem :)


FWIW, the problem still existed in 2.49.1 from 20170528045907
Which is expected since you FIXED the bug in August...

What does the .1 mean? When will it increase to .2?

Regards.



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