(I know there are possibly already tons of mails about this, but they're not in public, so...)
Although this looks like a release team decision (according to the wikipage), and we may have serious reasons to land it before Whistler, I don't think spark features are less risky. In fact, the exclusive planning and implementing workflow make it more risky than other ordinary feature sets or releases. For example, recently I have been NIed the hardware camera button bugs, because the *landed* implementation on spark device apparently considers no LockScreen in mind. However, since I was totally out of such feature designing and implementation (or I would tell you it's not naïve as you thought), I could only reply the NI to explain I can't help out. And now, I don't even know whether the code would follow the existing patterns between System and LockScreen, so for me (and the current LockScreen logics), it's *risky*. Of course for this case there are already lots of murmurs about our phone would be no LockScreen anymore (another thing so exclusive and not open: as an untitled owner obviously I'm the only one strongly affected but entirely out of discussions), so maybe the bug would be INVALID soon. BTW, I don't know why we looks like to have no standard working model for "risky" patches. I mean, as Vivien mentioned, and what I've seen in other OSS projects, to create a new branch for such radical changes is a 100% rational action. Also, I think this question occurs in my mind since 1.3 ~ 1.4, that we seem to treat our 'master' as a 'stable' branch, rather than a 'nightly' branch that allow people to taste the most edging features with the unstable risks (so where is our 'nightly' branch?) . I wonder if this is because we now only have the most fully covered CI infrastructure and test flows for 'master', so people can't expect the edging features got fully tested if they live in another branch? 2015-06-08 3:50 GMT+08:00 Vivien Nicolas <[email protected]>: > Can't you just branch so people can continue to work as usual without any > risk to disturb your launch ? > > On Sat, Jun 6, 2015 at 2:21 AM, Douglas Sherk <[email protected]> wrote: >> >> Hi all, >> >> Spark is launching soon. It's based on Gaia master and Gecko >> mozilla-central, so we'd appreciate it if you avoided landing risky patches >> for 3 weeks while we stabilize. Alternatively, you could have your patches >> tested very heavily before landing. >> >> You can see our current timelines here: >> >> https://wiki.mozilla.org/Release_Management/B2G_Landing#Versions_and_Scheduling >> >> Thanks for your patience and understanding. >> >> Doug >> >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g >> > > > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
