Bug#465696: developers-reference -- Please document more about the buildd and release processes
Hi, On Thu, Feb 14, 2008 at 09:36:55AM +0530, Kumar Appaiah wrote: Package: developers-reference Version: 3.3.8 Severity: wishlist Dear Developer's Reference maintainers, In the current state, the reference is mostly incomplete or silent about several of the release and package building related processes. What this means is that release managers often spend time explain to people whether/why something has to be done, and this keeps happening often. The reason for this is that the information on several of these aspects is currently spread in the Debian website, the Debian Wiki and some other resources. In order to ensure that knowledge of best practices related to relase, library transitions etc. are transmitted effectively to developers, I would request you to please consider adding or expanding the following sections to the reference: * buildd: How the buildds work, packages queued for build etc., where the buildd logs are found, how to react if a package is not built on an architecture where it actually should be built (describe the situations where give back is needed, and how to do it), how to react to problems on architectures which one cannot solve (e.g. ICE on a buildd whose architecture the developer does not have access to). (This would encompass #258437 as well.) * library transitions: What are the conditions which warrant a consultation with release managers before uploading a package which would involve a library transition, and what are the best practices associated with this. * binNMUs: Document the best practices for binNMUs, where and how to request for these. Pending your feedback, I would volunteer to collate information on these by asking the right people and reading the right pages. Thank you. Kumar You know Debian is volumteer organization. The best way to get things done is do it yourself. Why not write up some thing and aask people to include. There is wiki.debian.org where you may use as platform. Osamu -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 You seem to have good technical background ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465696: developers-reference -- Please document more about the buildd and release processes
On Thu, 14 Feb 2008, Kumar Appaiah wrote: * buildd: How the buildds work, packages queued for build etc., where the buildd logs are found, how to react if a package is not built on an architecture where it actually should be built (describe the situations where give back is needed, and how to do it), how to react to problems on architectures which one cannot solve (e.g. ICE on a buildd whose architecture the developer does not have access to). (This would encompass #258437 as well.) * library transitions: What are the conditions which warrant a consultation with release managers before uploading a package which would involve a library transition, and what are the best practices associated with this. * binNMUs: Document the best practices for binNMUs, where and how to request for these. Pending your feedback, I would volunteer to collate information on these by asking the right people and reading the right pages. I agree that all this documentation is lacking. However it's a big chunk of work to create that missing documentation. buildd are well documented on the website and Wouter Verhelst has written most of it. Maybe we can simply give pointers to the doc on the website and expand a bit more on the developer-side of the buildd management. In any case, feel free to go ahead and try to provide patches. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/
Bug#465696: developers-reference -- Please document more about the buildd and release processes
Package: developers-reference Version: 3.3.8 Severity: wishlist Dear Developer's Reference maintainers, In the current state, the reference is mostly incomplete or silent about several of the release and package building related processes. What this means is that release managers often spend time explain to people whether/why something has to be done, and this keeps happening often. The reason for this is that the information on several of these aspects is currently spread in the Debian website, the Debian Wiki and some other resources. In order to ensure that knowledge of best practices related to relase, library transitions etc. are transmitted effectively to developers, I would request you to please consider adding or expanding the following sections to the reference: * buildd: How the buildds work, packages queued for build etc., where the buildd logs are found, how to react if a package is not built on an architecture where it actually should be built (describe the situations where give back is needed, and how to do it), how to react to problems on architectures which one cannot solve (e.g. ICE on a buildd whose architecture the developer does not have access to). (This would encompass #258437 as well.) * library transitions: What are the conditions which warrant a consultation with release managers before uploading a package which would involve a library transition, and what are the best practices associated with this. * binNMUs: Document the best practices for binNMUs, where and how to request for these. Pending your feedback, I would volunteer to collate information on these by asking the right people and reading the right pages. Thank you. Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036 signature.asc Description: Digital signature
