On 11/17/2010 10:03 PM, Nishanth Menon wrote:
Arjan van de Ven had written, on 11/17/2010 03:51 PM, the following:
[Gorby, Russ]
So you're saying (more or less) that a prerequisite to meego
acceptance is upstream acceptance??
eventual upstream acceptance is a hard requirment yes (within 3
months or so).
basically given that -next is usually ~3 months timeframe now a days,
the current patch must:
a) be either in master of kernel.org
OR
b) be in next branch of a maintainer
depending on the maintainers, major feature addition stops being taken
in their next branches around rc3 or so to allow the features to
stabilize to be ready for next merge window.
.36 rc1 rc2 rc3 rc4 rcx 37 rc1
X-----*-----*-----*-----*-----*-----X-----*
|--#--|------------------------------------> old features
------------------> my new feature time frame
maintainer -next??|<------------------># merged here
so to meet this criteria, my patch should be posted at least before
.36 to make it into and accepted into for-next of maintainer in time
for .38 official kernel feature.
So what do we mean by the subjective statement "eventual upstream
acceptance"? I would say "eventual upstream acceptance" is possible
only if it is in maintainer's - for-next branch. Is that the criteria?
if the maintainer accepts it (and thus it hits -next) that's good
enough/upstream enough for me (in the 3 month sense)
_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
