p*******m
发帖数: 20761 | 1 As a oneplus one owner, and an avid flasher this leaked roadmap makes me
very excited. The source code to Android L is expected to be released
November 3rd, next Monday, and this means all those developers can get to
work. CyanogenMod has their plans set and I hope they can keep to it because
it is quite impressive. On November 3rd they will begin creating CM12
branches, then November 7th they are going to be releasing CM11 M12 and
stopping all new development except bug and vulnerability fixes to CM11,
next is the big one, they have a tentative release date of December 1st for
the first nightlies of CM12. More impressively they are claiming they will
have 50% of CM11 features and this is all in under a month. Let’s hope they
can stick to it and bring that goodness to devices all around. The new year
will bring the first M release then after that we should see the monthly
release and completely stable development to continue on. Please don’t let
me down CyanogenMod! You can read a lot more in the leaked document after
the break.
Gadgetspot
The plan:
CM 11 will go into Feature Freeze at the end of the week L code becomes
available. For the purposes of this post, I will use Novemeber 3rd as the
example date of AOSP drop.
Timeline:
# October 31st, CM 11 M12 branching begins
# November 3rd, AOSP releases code to L – all hell breaks loose. CM 12
branches will be created for all relevant projects and AOSP code will be
replicated to CM Github. See below for breakdown of CM 12 tasks.
# November 7th, CM 11 M12 released
# November 7th, CM 11 code enters Feature Freeze – all pushes to this
branch after this date should be directly tied to addressing a bug or
vulnerability. Device merges through DevRel will still be accepted,
translations and kernel/device tree changes can continue. Feature Freeze
will primarily impact CM apps and Framework – so get your features in ASAP
if you have stuff waiting.
# December 1st (tentative) – Nightlies for CM 12 begin, with 50% of CM11
features ported to CM12
# January 2nd, 2015 (tentative) – M releases for CM 12 begin, with feature
parity with CM11
# February 2015 – M2 and back to standard monthly releases
Items we are discussing:
1) Should we sign these builds with non test_keys?
2) Device cutoff based on specifications. We expect 512mb devices to be fine
, but the issue here will be GPU and non-Kitkat binaries. Expect a hard line
here drawn in the sand with respect to device support. This will not be
pretty for many older generation devices (pre-ICS).
3) Death of CWM Recovery and impact
4) Unification (see Bringups below)
Items not up for debate:
1) Watering down of SELINUX protections or Encryption by default. These are
base protections L is introducing and we should support these items as such.
If your device fails to allow encrypting, it will not get a CM sanctioned
release.
CM 12 Task list:
We will have the added resources of Inc. assisting us in this effort. As
part of this, I will have a Spreadsheet and JIRA project setup to assist in
coordination and non-duplication of efforts. If you see something you want
to own (that is non-assigned) please feel free to take ownership of it. More
on this as the date approaches. Please create a JIRA account if you don’t
have one yet.
CAF will play a heavy factor here as well – expect to see a healthy amount
of patches come from there in addition to AOSP.
Device bringups:
With the new Nexus devices coming online, the new and existing Nexus
platforms will likely be returned to their AOSP configs and move forward
from there. For other devices, you all are aware of your own items more than
I.
On this note – as a lesson learned from CM11, we need to be a bit smarter
when it comes to inheritance, dependencies and unification. I know this item
has been in debate before, but I strongly think we should not unify GSM and
CDMA variants of platforms. Further, devices that we do not own should not
be added to the ‘supported’ column.
Translations:
MB is taking ownership of this and will likely make a new CM 12 project on
translate.cyanogenmod.org |
|
