一楼.....

原文：
Goodbye unified, we hardly knew you
Observant readers will notice that the device variants, particularly for Samsung and Moto devices have once again been broken out into individual builds, counter to ourannouncement for CM11.
We are officially reverting the decision of using unified builds, as mentioned in that post, with CM12 and beyond.
We’re always conscious of build times, maintenance overhead and other common issues plaguing our contributors. The unified builds, at the time, proved to be an answer for a lot of those headaches – instead of pushing a change to 3-4 device repositories, we could make just one change. Instead of building 3-4 times, our maintainers could use one build to test across all variants. It sounded ideal, and was worth the effort.
So why the retraction? As you are all likely aware of, different carriers and regions receive updates to stock firmware at (putting it nicely) odd intervals. That means even if the device shared 95% of the same guts, the firmware wouldn’t necessarily be compliant across all the device variants. This was particularly prone to failures when looking at items like sensors and NFC. The effect snowballed, d2 and jf users will no doubt chime in here, and the overall quality of release for these unified devices fell.
We’re not ones to hold onto failed ideas, more about iteration and learning, and so we’ve reversed that prior decision. You’ll still be able to update from your CM11 unified to CM12 device variant release, but we will be abandoning the unified builds, and instead focusing on project structures that allow us to make use of ‘–common’ projects (ex. Jf-common). So, look out for jflteatt, spr, tmo and the other variants as their own builds moving forward. Motorola devices like the xt907, xt925, and xt926 share the same story and are likewise de-unified in CM12.

这话是什么意思，指的是moto设备将能得到更新但会对刷机包的内容和版式进行更改，不能通刷？还是直接不能升级CM12？

不懂帮顶

大海就这意思

反正都是蹭907的包 怕什么

哪位哥们用有道翻译一下

　　原文:
　　再见了统一,我们几乎不认识你
　　细心的读者会注意到,设备变异,尤其是三星和摩托设备再次被打破到个人构建,计数器为CM11 ourannouncement。
　　我们是正式恢复使用统一的决策构建,在文章中提到过,CM12和超越。
　　我们总是有意识的构建时间,维护开销和其他常见问题困扰我们的贡献者。统一构建,当时,被证明是一个答案对很多这些难题——而不是推动改变3 - 4设备存储库,我们可以只有一个变化。建立3 - 4次,而是我们的维护人员可以使用一个构建测试所有变体。听着理想,是值得努力的。
　　那么为什么撤回?你都可能意识到,不同的航空公司和地区接收更新股票固件(把它很好地)奇怪的间隔。这意味着即使设备共享95%的相同的勇气,固件未必是所有设备兼容的变体。这是特别容易失败时看着传感器和NFC之类的东西。效果打雪仗,d2和摩根富林明用户无疑会在这里,一致和统一发布这些设备的整体质量下降。
　　我们没有抓住失败的想法,更多关于迭代和学习,所以我们改变了之前的决定。你仍然能够更新从你CM11 CM12设备变体版本统一,但是我们将放弃统一的构建,而不是专注于项目结构,允许我们使用“普通”项目(例Jf-common)。寻找jflteatt,spr,tmo和其他变量构建自己的前进。摩托罗拉设备像xt907、xt925 xt926共享相同的故事,同样在CM12联署致歉。

有道翻译的

貌似以后可以进行通刷了。

不一句句的说了 大意就是因为三星和摩托的设备的问题 以后CM12没有统一版本的rom了 因为统一的版本会带来很多问题 本来只要在一个设备上测试 但是因为是统一的版本 所以要测试多个设备 问题反而变得麻烦 如果不用统一版本的话 就会方便很多