更新 & 版本准备(LineageOS 初版发布)

好了,好了,好了。是时候发布了。在大家激动下载之前,我们希望大家能注意以下几点。

首先,我们想要感谢那些继续支持我们建设(以及倾力帮助我们)的朋友们。感谢你们,我们所有的服务器目前已开始正常运行,各位可以在我们的状态页面查看。

此外,我们的 下载页面安装统计(对,目前已经有了超五万的非官方 ROM 安装量)和 Wiki 都已上线。值得一提的是,这三个页面,还有 Lineage 博客都是开源的。你可以通过我们的 Gerrit instance 贡献代码!请原谅目前我们网站的简陋,在我们前行的路途中我们将继续完善这些东西。

有趣的部分来了 —— 创建序列、发布过程和其他的一些详情:

  • 我们所支持的设备正在增长,但是我们将支持能够运行 Marshmallow 和 Nougat 的设备。 - 我们将会在另一个单独的文章里发布所支持的 80+ 设备。
  • 我们的发布周期默认将为“周”(给所有 donated 硬件)。
  • 我们将不会给 ROM 自带 root 权限。 - Root 将会像刷入 gapps 一样,提供在 zip 包里(仅需刷入一次)。
  • 如果自己想植入 su 进入到 ROM 中,可以运行 ‘export WITH_SU=true’ prior to building.
  • 为了验证和签名权限控制,我们将会在官方版本里通过私钥签名。 - 这并不会中断、妨碍或是阻止“非官方”版本的发布。
  • 密钥验证信息可以在 Wiki 的 Verifying Build Authenticity 页面 找到。

在安装方面,我们建议用户在切换到 LineageOS 时能清除数据,重新安装 gapps。我们也知道这的确很花时间,所以我们提供了一个实验性(如果出现问题,你依然需要清除数据)的措施。

  • 为了“周版”更新,我们提供了一个数据迁移的实验性版本。
  • 这个方案将使你从 CM “升级”到 已签名的 LineageOS 周版。
  • 但这个方案可能会使你的权限(你会被再次要求进行 app 的权限管理)遗失,但是将会保留所有的用户数据。
  • 这个版本将会打上一个丑的水印以保证你不会一直使用这个实验性版本,并确保之后你能更新到正常的实验性版本。
  • 过程如下: - 在 cm-13.0 或 cm-14.1 的版本(不要在 CM 14.1 以上版本安装 LineageOS,这不起作用)上安装实验性迁移版本(migration build)。
  • 重启
  • 安装 LineageOS 周版
  • 重启
  • 重设 App 权限

鉴于此过程的实验性质,我们将在两个月内删除此方案。

在本周末等着发布吧。

LineageOS 团队

ciwrl 写于 2017 年 1 月 20 日

Update & Build Prep

Alright, alright, alright – it’s nearly ‘go time’ for builds to start flowing. Before everyone gets excited and rushes to download, we want to cover a few important points.

First, we want to thank everyone that stepped forward to assist with the infrastructure (and offers continue to pour in). Thanks to you all, all infrastructure pieces are lighting up ‘Operational’ on our lovely status page.

Additionally, our Download Portal, Install stats page (yep, that’s 50k+ unofficial installs already!) and Wiki are all live. Notably, all three of these sites (and Lineage blog) are open sourced – you can contribute to them via our Gerrit instance! Bear with us if these sites look bare at the moment, they will grow with content and design as we continue marching forward.

On to the fun stuff – build roster, release process and other details:

  • The build roster is ever growing, but we are supporting Marshmallow and Nougat capable devices. - We’ll list the 80+ devices in a separate post.
  • Our release cadence will be ‘weekly’ by default (to be nice to all the donated hardware).
  • We will NOT be shipping root baked into the ROM. - Root will be a downloadable zip based install similar to gapps installation (only need to flash it once).
  • Home builders that want to bake su back into the ROM can use the command ‘export WITH_SU=true’ prior to building.
  • Our official builds will all be signed with a private key for authentication and signature permission control - This will not break, prevent or stop any ‘unofficial’ builds.
  • Key verification info can be found on the wiki Verifying Build Authenticity page

Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution.

  • Alongside the ‘weekly’ release for your supported device, we’ll provide an EXPERIMENTAL data migration build.
  • This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly
  • This build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user data
  • This build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.
  • The process for this installation will be as follows: - Install EXPERIMENTAL migration build on top of cm-13.0 or cm-14.1 build (don’t try to install LineageOS 13.0 on top of CM 14.1, that will not work).
  • Reboot
  • Install LineageOS weekly build
  • Reboot
  • Re-setup your application permissions

Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time.

Look for builds to start rolling out this weekend!

LineageOS Team

Written on January 20, 2017 by ciwrl