Look without wanting to get into a political discussion, and trust me from the glimpse of your politics revealed in your posts you would not want to discuss this with me neither 
The actual developers that initially forked decided to re-unite, if you were willing to give them the benefit of the doubt for the fork, why not give the the same latitude and trust now with the merge?
Best Regards
@moeller0
Well, I give it to you, after all, 2 posts earlier - I give you the chance to merge ... but not in this way like now because it simply wipes out the work and the creation of LEDE ... and the involvement of all concerned in this project of time and work, not just some imaginary developers. Therefore, from this ideological point of view, I see a contradiction in this decision, which, perhaps, I think too harshly as the beginning of the end of this project.
Separation from the leading role of LEDE, which symbolizes even the name after the connection "OpenWrt" gives you a guess in which direction it is going.
EDIT:
A description of my country's political situation through the eyes of a Pole and a patriot, and not, for example, some proverbial Israeli / German / or other parliamentary or senator denomination to the Seym of the Republic of Poland, who favors being a Pole by just a surname, which has resulted in such and no other policy for the last 20 years - it was just such a curiosity and canvas and a reference to the situation of LEDE / OpenWrt projects. Whether it's hit or not, it's just a question of the perception of the readers.
Here I will politely leave the discussion; what ever your gripe is it clearly is only remotely related to lede/openwrt including fork and re-merge. Since I have no information relevant to your interest, and you seem to not actually want to discuss/read about the lede/openwrt story, I think for us to discuss further would be a waste of time. Every discussion has its time and place and this seems not the place for ideology/politics IMHO.
Let's keep it polite and technical and let's not descend into prejudices and hostility (I am not claiming you attempted that*, but let's not go there), but rather follow lede's rule #12 (https://lede-project.org/rules) and be nice to each other.
Best Regards
) Actually re-readig your post I take that back; you comments are clearly incendiary in nature and inappropriate for this forum. Anti--isms do not get any more tolerable by replacing individual words.
@moeller0
Well, of course you can express your opinion about LEDE, just like me - everyone has the right to do so. I have a different one, You have a different one - that's it. Just be kind enough not to teach me what to do, what to write or not. Because you do not have such a right nowhere and anywhere - the freedom of speech is valid everywhere. It is clear that you do not understand the idea of an abstract comparison.
I greet you too ... hehe.
All I want to know is the name Lede officially depreciated or even DEAD?
Hence, should namespaces now be .openwrt not .lede?
@build000 think Brexit 
if a router is running lede and one has to upgrade to the latest openwrt builds, is unticking "Keep settings" and flashing openwrt-x-sysupgrade.bin enough?
EDIT: yep upgrade went just fine. Im curios if it worked even if I kept the "Keep settings" checkbox ticked
Freedom of speech does not imply everyone's right to write anything in this forum thread. Forum rules, thread topic and general common sense still apply.
There is no need to untick keep settings when updating from LEDE to Openwrt-branded LEDE builds.
LEDE codebase survives the merge and has just been rebranded as Openwrt. Currently LEDE master buildbot is creating Openwrt-branded builds and those snapshot builds are available from the LEDE download site.
Old Openwrt codebase is ancient and will be deprecated. Openwrt buildbot is still crunching binaries from that old code, and those trunk snapshot builds from the Openwrt download site should not be used. (There has been practically no development on the old Openwrt since April 2016 when active devs split off to LEDE.)
Crudely said, the whole merge is pretty much about renaming the current LEDE to Openwrt and organising the combined infra.
thanks for the detailed answer, appreciate it
@moeller0
I do not know what this anti-Semitism is about and I do not see it in my speech - if you see it, take my apologies - and by the way of this particular -ism, ask for an explanation of the Nazi invader or his descendants, who killed 5 million Poles and countless citizens of Jewish nationality in, for example, the Auschwitz-Birkenau ( https://en.wikipedia.org/wiki/Auschwitz_concentration_camp ) concentration camp (Oświęcim). As for the merits of the case on the technical forum, I have already expressed my opinion.
I wonder if there's a way to automatically close a topic once Godwin's law has been triggered.
I had to look that one up... there are some FUNNY google image hits for it 
@hnyman, I still don't understand why the Lede-team would choose to go back to using the old OpenWRT name, unless one of the original founders of OpenWRT choose to fork Lede and now wants the name back. Any other reason doesn't make sense. Lede is (should I say "was") building a good name for itself, actively developed and supported by a growing number of enthousiast (like myself).
Why would anyone choose to go back to a "brand-name" with a bad reputation?? As you said: nothing changed in the OpenWRT side of things since basically 2015 after the release of CC 15.x and people have noticed that. A lot of references were already to Lede on the OpenWRT forum (as you know) which made the major OpenWRT community more aware of our Lede-project. And I say "our" because like myself, a large group of people on this forum feel more connected with Lede than with OpenWRT because we want to support this project and their developers and we want this project to move forward.
When you breakup a partnership because it doesn't work out (business or personal), getting back together is almost never a good idea: The reasons why you broke up in the first place are there still there unless both partners made some major changes. I guess it's too late now: let's hope this is not beginning of the end.
Chiming in with my two cents: LEDE/OpenWRT are free projects, people are volunteering their time, I say we try to be more understanding and grateful that development is still ongoing no matter what name it takes on.
When everything settles out, the name LEDE will be a historic note in the
documentation. It will not be used anywhere in the project.
Now, it will probably take a long time to get to that point.
(I'm not sure exactly what namespaces you are talking about)
Exactly - I fully share your view - in fact, it was more or less what I wanted to write, but you managed to dress it in a more coherent whole (before I let myself be drawn into this Nazi / Zionist debate with others).
I believe I've posted this before too - both websites need info posted prominently on their front pages.
Purely as a user (not a dev), I support the merge, as LEDE is a fork of, and de-facto the current implementation of, OpenWRT. Additionlly, OpenWRT has the name recognition - when it was time for me to update my devices, it took multiple attempts before I even discovered that LEDE existed. If you want the project to survive, and thrive, get the merge done quickly, post the news, and get the word out to the tech sites.
Anyone upset by it is a bit late to the party, but if you wish to be involved, looks like the lede-adm list is where you should start. http://lists.infradead.org/pipermail/lede-adm/2017-November/000670.html
I have no idea why people are talking about Poland or Nazi's.
As an ancient OpenWRT developer that hasn't been around for a while. this seems nearly identical to the DD-WRT fork except LEDE wasn't trying to run away and make a pay-for version like scum. I used to do quite a bit of backporting of the things DD-WRT went forward with (specific focus on destroying market share by cloning their "paid" features) to bring the features back to OpenWRT. Same with other mild-forks like Gargoyle or Tomato, it's OpenWRT with a new facade on it.
This stupid backflip is no different. There will always be forks unless the "management" stops being however it is they are that causes forks. But OpenWRT is the genesis of every router firmware, almost.
I prefer going back to the name that started it all, OpenWRT. I didn't know LEDE even existed until the other day, literally never heard of it. Everyone knows OpenWRT.
That being said WPN824N doesn't work correctly anymore you guys broke it compared to OpenWRT trunk... and I had a pile of fixes for OpenWRT trunk that improved it exponentially, but when applied to LEDE trunk the LED triggers don't work right and a bunch of other problems that weren't there before. So again, JUST like the DD-WRT split...
OranguTech has hit the nail on the head here; this needs to be very visible and not buried away in a forum. I got interested in LEDE because of Cake (on an Archer C7) which works very well. I was also impressed with the speed that 17.01.4 was rolled out to patch the Krack vulnerability. I keep a virtual router available on Virtual Box which I update with snapshots from time to time to see if I'm missing anything or need to update my actual routers. I updated it today and was surprised to see the OpenWRT branding, and it took a bit of digging to find this forum thread. It really shouldn't have taken any digging, it should have been on page NUMERO UNO. I really have no view on whether the change is good or not, it's entirely up to the devs, but I really don't want to panic when I see that a different image has been loaded to what I expected.
I don't see how it's similar at all. Look more into the reasons for the LEDE split and you'll see that this really wasn't a destructive fork. It was a last-resort act that actually moved things forward.
LEDE was essentially almost the whole current active developer community of OpenWRT breaking away from the control of the original project founders, who they felt were making development too difficult with their inertia and slack management of key project infrastructure. Hardly a fork at all, more like a rebellion and continuation under new management.
This is why the original OpenWRT essentially died from the moment LEDE was founded. The "re-merge" is really more like a re-brand, where the OpenWRT owners have admitted defeat and agreed to get on board and give the cherished brand to the continuing project, rather than let it die.
It's unfortunate that you were out of the loop. I don't know what caused the breakage of your WPN824N work, but it would likely have happened either way. The problem here is the fact that you had to maintain a separate "pile of fixes" in the first place. Now it should be much easier to get your work merged into the tree where it belongs.