On 12/14/2010 1:45 PM, Carsten Munk wrote:
Hi,
Just noticed that http://wiki.meego.com/Core_OS_Program/Kernel_policy
came up and is on the agenda for TSG meeting tomorrow, so given that
we have 24 hours to comment and I haven't seen it discussed in public,
here's a couple of questions/comments from a hardware adaptation PoV
(not speaking from N900 PoV):
Before I start on a rather long reply - the proposal looks great, will
hopefully make some things clearer.
6. The adaption kernels must follow the same release process/timing as the rest
of MeeGo; e.g. the same feature freeze, code complete dates etc etc.
(nitpick since we're making this into policy: 'adaptation' not 'adaption')
So, I'd like to ask how we will deal with the following situation that
well may arise:
* Vendor comes with a hardware adaptation for device/platform X and
wants to contribute this for MeeGo. This contains an adaptation
kernel. It passes all automatic core OS testing and is deemed
compliant for 1.2. Vendor naturally wants to contribute this for MeeGo
1.2 device makers to use. Problem is that 1.2 timeframe has gone and
passed, so he can't participate in normal release process but yet it's
a perfectly fine hardware adaptation.
ok the intent was to describe the things that would release as part of
the "official" Meego.com release at the time of release.
If someone comes in later with a kernel great, but that's not part of
the "day 1 official release announcement" kind of stuff.
for that to be the case, you need to be part of the whole release
process, not show up 1 week before the official release and drop a bunch
of stuff in.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
