dc7 - 1.0
DebConf7
| Speakers | |
|---|---|
|
Anthony Towns |
| Schedule | |
|---|---|
| Day | 8 |
| Room | Upper BoF Room |
| Start time | 15:00 |
| Duration | 02:00 |
| Info | |
| ID | 110 |
| Event type | Open discussion (BoF) |
| Track | DebCamp |
| Language | English |
| Feedback | |
|---|---|
|
Did you attend this event? Give Feedback |
dak future direction BOF
Discussion and brainstorming about possible improvements to the debian-archive-kit with a view to getting them implemented during debcamp/debconf.
Ideas so far:
- work out how to do separate staging areas, so a "KDE" staging area and a "C++ abi bump" staging area can be created, and merged into unstable independently... Refer to Rob Collins' talk at the debian miniconf at linux.conf.au 2007.
- have some call out at ACCEPT time to piuparts or other automated testing infrastructures, so we can give a quick REJECT to packages that don't work right. need to cope with piuparts/whatever possibly taking a while to run. likewise automatic lintian/linda REJECTs, though they could happen directly on ftp-master
- integrate Thomas Viehmann's dak examine-package patches if it's not already done (Bug#408318)
- integration of debian-edu, debian-volatile or backports.org ?
- work out how to do "short-term support" releases of testing and d-i? cf joeyh's CUT
- get a public, permanent archive of all sources uploaded to Debian available (source-morgue.d.o)
- an experimental archive for playing with new ideas for structuring the archive? (new architectures that might undergo massive abi changes, new rules for uploading, new suites, new rules for transitioning between suites, etc?)
- move Sources.gz to using SHA1 or SHA256 hashes instead of / as well as md5?
- move .changes to using SHA1 or SHA256 hashes instead of md5?
- automated acceptance of certain byhand uploads (tags updates, etc)