思维导图备注

Debian Developer's Reference 11.0.16 Documentation
首页 白天 夜间 BookChat 小程序 小程序 阅读
  • 书签 我的书签
  • 添加书签 添加书签 移除书签 移除书签

3. Debian Developer’s Duties

 来源:debian 浏览 330 扫码 分享 2020-11-14 08:08:22
  • 3. Debian Developer’s Duties

    3. Debian Developer’s Duties

    • 3.1. Package Maintainer’s Duties
    • 3.2. Administrative Duties
    当前内容版权归 debian 或其关联方所有，如需对内容或内容相关联开源项目进行关注与资助，请访问 debian .
    上一篇:
    下一篇:
    • 书签
    • 添加书签 移除书签
    • 1. Scope of This Document
    • 2. Applying to Become a Member
      • 2.1. Getting started
      • 2.2. Debian mentors and sponsors
      • 2.3. Registering as a Debian member
    • 3. Debian Developer’s Duties
      • 3.1. Package Maintainer’s Duties
        • 3.1.1. Work towards the next stable release
        • 3.1.2. Maintain packages in stable
        • 3.1.3. Manage release-critical bugs
        • 3.1.4. Coordination with upstream developers
      • 3.2. Administrative Duties
        • 3.2.1. Maintaining your Debian information
        • 3.2.2. Maintaining your public key
        • 3.2.3. Voting
        • 3.2.4. Going on vacation gracefully
        • 3.2.5. Retiring
        • 3.2.6. Returning after retirement
    • 4. Resources for Debian Members
      • 4.1. Mailing lists
        • 4.1.1. Basic rules for use
        • 4.1.2. Core development mailing lists
        • 4.1.3. Special lists
        • 4.1.4. Requesting new development-related lists
      • 4.2. IRC channels
      • 4.3. Documentation
      • 4.4. Debian machines
        • 4.4.1. The bugs server
        • 4.4.2. The ftp-master server
        • 4.4.3. The www-master server
        • 4.4.4. The people web server
        • 4.4.5. salsa.debian.org: Git repositories and collaborative development platform
        • 4.4.6. chroots to different distributions
      • 4.5. The Developers Database
      • 4.6. The Debian archive
        • 4.6.1. Sections
        • 4.6.2. Architectures
        • 4.6.3. Packages
        • 4.6.4. Distributions
        • 4.6.5. Release code names
      • 4.7. Debian mirrors
      • 4.8. The Incoming system
      • 4.9. Package information
        • 4.9.1. On the web
        • 4.9.2. The dak ls utility
      • 4.10. The Debian Package Tracker
      • 4.11. Developer’s packages overview
      • 4.12. Debian’s FusionForge installation: Alioth
      • 4.13. Goodies for Debian Members
    • 5. Managing Packages
      • 5.1. New packages
      • 5.2. Recording changes in the package
      • 5.3. Testing the package
      • 5.4. Layout of the source package
      • 5.5. Picking a distribution
        • 5.5.1. Special case: uploads to the stable and oldstable distributions
        • 5.5.2. Special case: the stable-updates suite
        • 5.5.3. Special case: uploads to testing/testing-proposed-updates
      • 5.6. Uploading a package
        • 5.6.1. Uploading to ftp-master
        • 5.6.2. Delayed uploads
        • 5.6.3. Security uploads
        • 5.6.4. Other upload queues
        • 5.6.5. Notifications
      • 5.7. Specifying the package section, subsection and priority
      • 5.8. Handling bugs
        • 5.8.1. Monitoring bugs
        • 5.8.2. Responding to bugs
        • 5.8.3. Bug housekeeping
        • 5.8.4. When bugs are closed by new uploads
        • 5.8.5. Handling security-related bugs
      • 5.9. Moving, removing, renaming, orphaning, adopting, and reintroducing packages
        • 5.9.1. Moving packages
        • 5.9.2. Removing packages
        • 5.9.3. Replacing or renaming packages
        • 5.9.4. Orphaning a package
        • 5.9.5. Adopting a package
        • 5.9.6. Reintroducing packages
      • 5.10. Porting and being ported
        • 5.10.1. Being kind to porters
        • 5.10.2. Guidelines for porter uploads
        • 5.10.3. Porting infrastructure and automation
        • 5.10.4. When your package is not portable
        • 5.10.5. Marking non-free packages as auto-buildable
      • 5.11. Non-Maintainer Uploads (NMUs)
        • 5.11.1. When and how to do an NMU
        • 5.11.2. NMUs and debian/changelog
        • 5.11.3. Using the DELAYED/ queue
        • 5.11.4. NMUs from the maintainer’s point of view
        • 5.11.5. Source NMUs vs Binary-only NMUs (binNMUs)
        • 5.11.6. NMUs vs QA uploads
        • 5.11.7. NMUs vs team uploads
      • 5.12. Package Salvaging
        • 5.12.1. When a package is eligible for package salvaging
        • 5.12.2. How to salvage a package
      • 5.13. Collaborative maintenance
      • 5.14. The testing distribution
        • 5.14.1. Basics
        • 5.14.2. Updates from unstable
        • 5.14.3. Direct updates to testing
        • 5.14.4. Frequently asked questions
    • 6. Best Packaging Practices
      • 6.1. Best practices for debian/rules
        • 6.1.1. Helper scripts
        • 6.1.2. Separating your patches into multiple files
        • 6.1.3. Multiple binary packages
      • 6.2. Best practices for debian/control
        • 6.2.1. General guidelines for package descriptions
        • 6.2.2. The package synopsis, or short description
        • 6.2.3. The long description
        • 6.2.4. Upstream home page
        • 6.2.5. Version Control System location
      • 6.3. Best practices for debian/changelog
        • 6.3.1. Writing useful changelog entries
        • 6.3.2. Selecting the upload urgency
        • 6.3.3. Common misconceptions about changelog entries
        • 6.3.4. Common errors in changelog entries
        • 6.3.5. Supplementing changelogs with NEWS.Debian files
      • 6.4. Best practices for maintainer scripts
      • 6.5. Configuration management with debconf
        • 6.5.1. Do not abuse debconf
        • 6.5.2. General recommendations for authors and translators
        • 6.5.3. Templates fields definition
        • 6.5.4. Template fields specific style guide
      • 6.6. Internationalization
        • 6.6.1. Handling debconf translations
        • 6.6.2. Internationalized documentation
      • 6.7. Common packaging situations
        • 6.7.1. Packages using autoconf/automake
        • 6.7.2. Libraries
        • 6.7.3. Documentation
        • 6.7.4. Specific types of packages
        • 6.7.5. Architecture-independent data
        • 6.7.6. Needing a certain locale during build
        • 6.7.7. Make transition packages deborphan compliant
        • 6.7.8. Best practices for .orig.tar.{gz,bz2,xz} files
        • 6.7.9. Best practices for debug packages
        • 6.7.10. Best practices for meta-packages
    • 7. Beyond Packaging[](#beyond-packaging “Permalink to this headline”)
      • 7.1. Bug reporting[](#bug-reporting “Permalink to this headline”)
        • 7.1.1. Reporting lots of bugs at once (mass bug filing)[](#reporting-lots-of-bugs-at-once-mass-bug-filing “Permalink to this headline”)
      • 7.2. Quality Assurance effort[](#quality-assurance-effort “Permalink to this headline”)
        • 7.2.1. Daily work[](#daily-work “Permalink to this headline”)
        • 7.2.2. Bug squashing parties[](#bug-squashing-parties “Permalink to this headline”)
      • 7.3. Contacting other maintainers[](#contacting-other-maintainers “Permalink to this headline”)
      • 7.4. Dealing with inactive and/or unreachable maintainers[](#dealing-with-inactive-and-or-unreachable-maintainers “Permalink to this headline”)
      • 7.5. Interacting with prospective Debian developers[](#interacting-with-prospective-debian-developers “Permalink to this headline”)
        • 7.5.1. Sponsoring packages[](#sponsoring-packages “Permalink to this headline”)
        • 7.5.2. Advocating new developers[](#advocating-new-developers “Permalink to this headline”)
        • 7.5.3. Handling new maintainer applications[](#handling-new-maintainer-applications “Permalink to this headline”)
    • 8. Internationalization and Translations
      • 8.1. How translations are handled within Debian
      • 8.2. I18N & L10N FAQ for maintainers
      • 8.3. I18N & L10N FAQ for translators
      • 8.4. Best current practice concerning l10n
    • Appendix
      • 1.1. Core tools
      • 1.2. Package lint tools
      • 1.3. Helpers for debian/rules
      • 1.4. Package builders
      • 1.5. Package uploaders
      • 1.6. Maintenance automation
      • 1.7. Porting tools
      • 1.8. Documentation and information
    暂无相关搜索结果！

      本文档使用 BookStack 构建

      展开/收起文章目录

      分享，让知识传承更久远

      文章二维码

      手机扫一扫，轻松掌上读

      文档下载

      • 普通下载
      • 下载码下载(免登录无限下载)
      你与大神的距离，只差一个APP
      APP下载
      请下载您需要的格式的文档，随时随地，享受汲取知识的乐趣！
      PDF文档 EPUB文档 MOBI文档
      温馨提示 每天每在网站阅读学习一分钟时长可下载一本电子书，每天连续签到可增加阅读时长
      下载码方式下载：免费、免登录、无限制。 免费获取下载码

      微信小程序阅读

      BookChat 微信小程序阅读
      您与他人的薪资差距，只差一个随时随地学习的小程序

      书签列表

        阅读记录

        阅读进度: 0.00% ( 0/0 ) 重置阅读进度