Randall Donald wrote: > You description says that new uploads are made for each kernel change, > but what about each driver version change?
In theory, a driver changes means binNMU of the conglomeration module package, scheduled by a release-team member as usual, on request of the module maintainer or the kernel team. In practise, especially because some more modules are expected to join in, it will be a reupload in order to ensure that the build of the new driver works prior upload. > I'm not sure if I read it right, but does maintainership of the kernel > modules packages transfer to you? not really. *Currently* (read the emphasis as 'this is how it is done atm, but if you come up with something better, there is no problem to change that), the conglomeration packages are maintained by the kernel-team, in real person that maps to Bastian and me. That means, that from the module source point of view, nothing changes. And for the binary builds only, that means, that the kernel team is listed as the maintainer, as they take care about/coordinate the builds/uploads. However, every bug which gets assigned to one of the binary modules is reassigned by me to the corresponding -source package. So, you are still the maintainer needing to take care and give love to the packages; you just don't need to care about the kernel abi transitions anymore and hence don't need to deal with NEW anymore. > I think I am interested in having the modules joining this project. Let me know if you would like to change something in the current scheme above. If not, I would then look at the modules and let you know (within this bug), if you need to adjust something. Regards, Daniel -- Address: Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
