What happens to Pale Moon when Firefox's Holly branch dies?

[jumba]

They don't read every comment -- but they do look for things such as "horrible", "awesome" to understand where things are going.

OR they count the swear words

[Moonchild]

They don't read every comment -- but they do look for things such as "horrible", "awesome" to understand where things are going.

OR they count the swear words

They probably automatically filter the swear words. And then they go "See, hardly any swearing going on, people love Australis!" (oh, the wonders of statistics)

[opera1215b1748]

Now you can understand my feelings about the Presto->Webkit transition in the someotherbrowser...

[Daikun]

https://mail.mozilla.org/pipermail/firefox-dev/2014-March/001487.html

You'll be missed, Holly branch.

[Moonchild]

Better grab your binaries of Holly while you still can...
I'll be pulling the latest hg updates and keeping a copy of the Holly source tree on my disk, just in case.

[Night Wing]

On the very first page of this topic, I said I thought Mozilla would kill off Holly when Australis got close enough.

[Daikun]

I'll be pulling the latest hg updates and keeping a copy of the Holly source tree on my disk, just in case.

Nice!

[Jonguy30]

It's too bad that "Australis" is getting forced down on everyone. Maybe even the next ESR will have Australis too?

[Moonchild]

Maybe even the next ESR will have Australis too?

Extremely likely, which is going to be a problem for corporate users.

[dark_moon]

So in the worst case..If firefox dies any day because they make their browser even more unusable.
What then?
It doesn't exist any other good browser which are OpenSource, secure and good.

[Moonchild]

Nobody is stopping me from permanently branching off from Mozilla any time I want.
I have no intention of letting Pale Moon die.

[dark_moon]

Perfect! Thats what i want to read

[Night Wing]

I think it's very safe to say Australis will be in the next Firefox 31 ESR version. I'd go all in and bet the farm on that.

[Sajadi]

Sure it is. Because Mozilla wants as fast as possible force feed everyone the "blessings" of their Mozilla Chrome!

[Moonchild]

As it is, it seems that the Holly branch, even though green in tinderbox, refuses to build on my dev machine. Probably something to do with Visual Studio 2012 because it wants to do something totally backwards when building libvpx... someone having the bright idea to make .obj code then pulling data from the .obj with an extractor...? I tried to build it just to have a look at the "final" state of that branch, but oy. No go.

I'll have to do some research as to why it won't build in vs2012. might be important for later versions of the Mozilla code as well, if it ever becomes a required switch.

[Night Wing]

I'll have to do some research as to why it won't build in vs2012. might be important for later versions of the Mozilla code as well, if it ever becomes a required switch.

I hope you can figure it out since Pale Moon, which is my default browser, affects me in both Windows and Linux.

[Daikun]

As it is, it seems that the Holly branch, even though green in tinderbox, refuses to build on my dev machine. Probably something to do with Visual Studio 2012 because it wants to do something totally backwards when building libvpx... someone having the bright idea to make .obj code then pulling data from the .obj with an extractor...? I tried to build it just to have a look at the "final" state of that branch, but oy. No go.

I'll have to do some research as to why it won't build in vs2012. might be important for later versions of the Mozilla code as well, if it ever becomes a required switch.

2012 isn't the latest version of VS. Maybe try upgrading to 2013?

If that doesn't help, why don't you give an alternate program a try?

I know they might not be as advanced as VS, but maybe you can use these for testing and analyzing any different results that may occur.

[Moonchild]

2012 isn't the latest version of VS. Maybe try upgrading to 2013?

I don't have half a grand to blow just to see if I can build an alt branch
Switching studio versions is also not trivial.

Besides, I think the problem is not "not having the latest" - Mozilla uses an older version; the code generated by vs2012 may not work for the extractor program (the risk of relying on this backwards method of getting data)

If that doesn't help, why don't you give an alternate program a try?

Your suggested alternate being Microsoft VS2008... That's not an alternate program.
Besides, I'm not going back to 2008 or 2010. VS 2012 has too many advantages for building (which is why it was bought to begin with).

[megaman]

I don't have half a grand to blow just to see if I can build an alt branch
Switching studio versions is also not trivial.

Didn't the switch start because you had a trial version of 2012 that you tested and it proved beneficial?
If it works, just set up another campaign.
I mean, it would be easier if it was VS every 3 years, like Office 2007, 2010, 2013. (On the wallets, of course)

The concern is when Holly dies, we lose customization? No other way? Unless build from scratch, right?

[Moonchild]

I don't see a reason to switch to VS2013, to begin with
It focuses heavily -- even more than 2012 -- on "Microsoft Store" (metro) app development which I'm not interested in.

And Holly has died. Looks like the UX team told Mike Conley to stop updating it with the move from Aurora to Beta.

The question is now: should I grab beta, and continue the work where it was left off, backing out Australis patches but keeping other patches? That's going to be a day job since I don't have the infrastructure to automate try builds; I don't have time for that, really.
In addition, Holly = FF29; that's not going to be the code base for the next ESR so it'll be a problem trying to keep it patched up.

I'll be better off doing what I planned, which is sitting the cycle out, seeing how Australis is received and what Mozilla does as a response, and work on 31ESR as a new code base when it's (near) completed.