User:Winterz: Difference between revisions

From KDE TechBase
No edit summary
No edit summary
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
= KDE SC Release Packaging Thoughts =
top-level layout


1. a CI system where we build all of KDE SC
project ->
  - no packaging unless all modules build ok
   autotests
    (even better would be to force all make tests too)
   docs
   - the packaging tools run on the CI system generating "test" tarballs.
   src
   - the "test" tarballs could be downloaded from the CI system
   tests
   -
   CMakeLists.txt
 
   COPYING, COPYING.LIB,... [all files dealing with the project license]
2. the KDE Sysadmin Team
   metainfo.yaml
   - provides and manages the CI system
   README.md
   - will transfer "test" tarballs to the public ftp site
   .reviewboardrc
   - prepares the public ftp site for bandwidth requirements at release announce time
   ProjectConfig.cmake.in
  -
   ProjectMacros.cmake
 
3. the KDE Promo Team
  - writes and distributes release announcements through normal channels
  - deals with the media
   - manages public expectations
   -
 
4. the KDE i18n Team
   - maintains the languages list
   -
 
* the KDE Release Team
  - coordinates the entire release effort
  - sets release milestones and dates
  - communicates important dates to the community and to distros
  - communicates important news to the community and to distros
  - creates "test" tarballs using the CI system and handles feedback
  - adds hot and security patches to the tarballs before the final release
  - creates "final" tarballs using the CI system
  - pushes tags to the module repositories in a timely manner
   -

Latest revision as of 15:47, 27 December 2015

top-level layout

project ->

 autotests
 docs
 src
 tests
 CMakeLists.txt
 COPYING, COPYING.LIB,... [all files dealing with the project license]
 metainfo.yaml
 README.md
 .reviewboardrc
 ProjectConfig.cmake.in
 ProjectMacros.cmake