On Wed, Apr 18, 2012 at 11:00:39AM +0000, Arnd Bergmann wrote: > 1. develop on -rc > 2. merge with latest -next, test and make sure it works there > 3. submit for review against -rc > 4. have patches included in -next once reviewed, but based on -rc > 5. when merge window opens, have patches sent for upstream inclusion Steps 3 and 4 should be to submit against whatever branch is appropriate for the subsystem and driver - if people follow this process they're going to get bounced back by a fair proportion of maintainers, -rc isn't universally what people are looking for so people should be aware that they need to pay attention here. Generally I'd say the development version is a safer bet than -rc for most subsystems.
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
