March 9th, 2010 | 
Author: 
http://packages.debian.org/sid/developers-reference – - Bcc: pts-news@qa.debian.org Subject: Galeon 2.0 backported for woody X-PTS-Package: galeon Hello gnomers! I’m glad to announce that galeon has been backported for woody. You’ll find everything here: … Think twice before adding a news item to the PTS because you won’t be able to remove it later and you won’t be able to edit it either. The only thing that you can do is send a second news item that will deprecate the information contained in the previous one. 4.11. Developer’s packages overview A QA (quality assurance) web portal is available at http:// qa.debian.org/developer.php which displays a table listing all the packages of a single developer (including those where theparty is listed as a co-maintainer). The table gives a good summary about the developer’s packages: number of bugs by severity, list of available versions in each distribution, testing status and much more including links to any other useful information. It is a good idea to look up your own data regularly so that you don’t forget any open bugs, and so that you don’t forget which packages are your responsibility. 4.12. Debian’s GForge installation: Alioth Alioth is a Debian service based on a slightly modified version of the GForge software (which evolved from SourceForge). This software offers developers access to easy-to-use tools such as bug trackers, patch manager, project/task managers, file hosting services, mailing lists, CVS repositories etc. All these tools are managed via a web interface. It is intended to provide facilities to free software projects backed or led by Debian, facilitate contributions from external developers to projects started by Debian, and help projects whose goals are the promotion of Debian or its derivatives. It’s heavily used by many Debian teams and provides hosting for all sorts of VCS repositories. All Debian developers automatically have an account on Alioth. They can activate it by using the recover password facility. External developers can request guest accounts on Alioth. For more information please visit the following links: * http://wiki.debian.org/Alioth * http://wiki.debian.org/Alioth/FAQ * http://wiki.debian.org/ Alioth/PackagingProject * http://alioth.debian.org/ 4.13. Goodies for Developers 4.13.1. LWN Subscriptions Since October of 2002, HP has sponsored a subscription to LWN for all interested Debian developers. Details on how to get access to this benefit are in http://lists.debian.org/ debian-devel-announce/ 2002/10/msg00018.html. Chapter 5. Managing Packages This chapter contains information related to creating, uploading, maintaining, and porting packages. 5.1. New packages If you want to create a new package for the Debian distribution, you should first check the Work-Needing and Prospective Packages (WNPP) list. Checking the WNPP list ensures that no one is already working on packaging that software, and that effort isnot duplicated. Read the WNPP web pages for more information. Assuming no one else is already working on your prospective package, you must then submit a bug report (Section 7.1, Bug reporting ) against the pseudo-package wnpp describing your plan to create a new package, including, but not limiting yourself to, a description of the package, the license of the prospective package, and the current URL where it can be downloaded from. You should set the subject of the bug to ITP: foo — short description, substituting the name of the new package for foo. The severity of the bug report must be set to wishlist. Please send a copy to [debian-devel@ lists.debian.org] by using the X-Debbugs-CC header (don’t use CC:, because that way the message’s subject won’t indicate the bug number). If you are packaging so many new packages (]10) that notifying the mailing list in seperate messages is too disruptive, do send a summary after filing the bugs to the debian-devel list instead. This will inform the other developers about upcoming packages and will allow a review of your description and package name. Please include a Closes: bug#nnnnn entry in the changelog of the new package in order for the bug report to be automatically closed once the new package is installed in the archive (see Section 5.8.4, When bugs are closed by new uploads ). When closing security bugs include CVE numbers as well as the Closes: #nnnnn. This is useful for the security team to track vulnerabilities. If an upload is made to fix the bug before the advisory ID is known, it is encouraged to modify the historical changelog entry with the next upload. Even in this case, please include all available pointers to background information in the original changelog entry. There are a number of reasons why we ask maintainers to announce their intentions: * It helps the (potentially new) maintainer to tap into the experience of people
Duration : 0:7:45
Posted in 
Tags:
FUK OFF
OFF