Differences between revisions 4 and 5
Revision 4 as of 2006-03-07 23:30:43
Size: 6136
Editor: zobel
Comment:
Revision 5 as of 2006-03-07 23:32:20
Size: 5414
Editor: zobel
Comment:
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
 1. We have currently six suites, woody-test, woody, sarge-test, sarge, etch-test and etch. Every suite generates a CD Image which should be tested. We seperate the suites into "normal" and "test". If you want to upload a package you have to upload it to the -test pool. After the package made it into the archive you can test the daily build image from the -test pool carefully. If your package/fix is working you should contact the ftp-team and request that the package will be moved into the ?normal? pool. With this procedure we guarantee a kind of stable development. Now some explanations of the suites: The woody* suites will only touched if a security update is available. For that purpose only the security team is able to upload to these pools. The sarge* suites can be touched if a security fix or a critical bug fix is made. For official DESA (DebianEduSecurityAnnouncement) updates only the security team is allowed to upload them. Packages with critical bugfixes can be uploaded by every Uploader. For the woody* and the sarge* suites it is not allowed to add real new packages. The etch* suites are the unstable suites where the normal development takes place. Here it is also important that you test your new implementations/packages, so we follow the procedure described above.  1. We have currently six suites, woody-test, woody, sarge-test, sarge, etch-test and etch. Every suite generates a CD Image which should be tested. We seperate the suites into "normal" and "test". If you want to upload a package you have to upload it to the -test pool. After the package made it into the archive you can test the daily build image from the -test pool carefully. If your package/fix is working you should contact the ftp-team and request that the package will be moved into the ?normal? pool. With this procedure we guarantee a kind of stable development.

Debian-Edu/Skolelinux Archive Policy

  1. Every Uploader has to accept the DFSG and the Debian Social Contract in order to have the same base for our work.
  2. The work on the three main packages (debian-edu, debian-edu-install and debian-edu-config) is done in Subversion, so only versions which can be found there are allowed to upload in order to guarantee the team maintenance on these packages.
  3. Normally we accept only packages which are also part of Debian. If for some reasons the package is not yet in Debian please write some notes into the changelog. If the package wont go into Debian for some reasons it is necessary to write a mail with a description and the reasons to ML (ftpmasters@skolelinux.org or debian-edu@lists.debian.org) to get your package accepted, but the general intention should be to get the package into debian one day.

  4. Please keep the number of backports to a minimum. If the backport is really needed for our system to run (e.g. new initrd-tools) it will be accepted. If the backport is optional (e.g. a new kde application) you get a better chance for acception if you write some comments into the changelog. (This is recommended but not needed) If the package will be rejected you have to discuss it with the ftp-team, their intention is to have a minimum of backports. Change their opinion about your backport and the package will be accepted. Please make sure that your backport is mostly bug free and already in Debian testing. Only by security fixes you should backport a package from unstable.
  5. If you intend to become a Debian-?EduDeveloper with upload rights yourself please write a mail to drift@skolelinux.org . In this case it makes no sense to write a mail to the ftp-team, although they can/will add you later to the keyring the permission to decide it only has drift. We don't recommend further skills in any area and you do not need to be an official Debian Developer to get upload rights. Please decide on your own if you should get upload rights and write the mail with your intentions and maybe some explanations. (Keep in mind with great power comes great responsibility). If you are not sure and you want to contribute and commit to Subversion and upload packages but you need some introduction/training in packaging you can ask for some help with writing it into the explanation to drift@skolelinux.org. Then drift will assign a Developer to you which helps you a bit in getting knowledge about Subversion, the Debian-Edu Development, packaging and uploading to the archive. (Maybe this is one of the ftp-team). This Developer tries to help you as fast as he/she can, please don't be angry if it takes some time he/she might be right busy but tries his/her very best to help you.

  6. If you upload a package you want to have it on the CD Image. We try to get our whole distribution on one CD and use the official Debian mirrors for any other package. If your package is not good enough to make it on the CD please drop it until it is good enough.
  7. We have currently six suites, woody-test, woody, sarge-test, sarge, etch-test and etch. Every suite generates a CD Image which should be tested. We seperate the suites into "normal" and "test". If you want to upload a package you have to upload it to the -test pool. After the package made it into the archive you can test the daily build image from the -test pool carefully. If your package/fix is working you should contact the ftp-team and request that the package will be moved into the ?normal? pool. With this procedure we guarantee a kind of stable development.
  8. In order to see the bugzilla interaction it is recommended that you write down in your changelog if you close a Debian-Edu/Skolelinux Bug (e.g. * foo bar (Closes Skolelinux Bug #007) ) but keep in mind that you have to close the bug manually in bugzilla!
  9. In addition to these rules we try to follow the normal Rejection-FAQ written by the Debian ftpmasters to make sure we keep the archive legal and keep the packages in good quality. You find their rejection-FAQ at http://ftp-master.debian.org/REJECT-FAQ.html

  10. The Uploaders are not anonymous. A current list can be found at ...
  11. This list is not complete and some new points might be added. So please make sure that you read it again from time to time.

Some explanations on the suites

  • The woody* suites will only touched if a security update is available. For that purpose only the security team is able to upload to these pools.
  • The sarge* suites can be touched if a security fix or a critical bug fix is made. For official DESA (?DebianEduSecurityAnnouncement) updates only the security team is allowed to upload them. Packages with critical bugfixes can be uploaded by every Uploader.

  • The etch* suites are the unstable suites where the normal development takes place. Here it is also important that you test your new implementations/packages, so we follow the procedure described above.

For the woody* and the sarge* suites it is not allowed to add real new packages.

Current ftp-team

The ftp-team is not anonymous. The current members are:

  • Morten Werner Olsen
  • Holger Levsen,
  • Martin Zobel-Helas and
  • Steffen Joeris

If you want to get in contact with them or if you just have some questions write a mail to:debian-edu@lists.debian.org or ftpmasters@skolelinux.org