[php-maint] roadmap for etch
seanius at debian.org
Tue Sep 19 06:31:41 UTC 2006
i think we should hammer out a roadmap for what we want to have
accomplished before etch hits the streets. here's some stuff off the
top of my head:
adding the phpfoo-mysqli packages. done in svn.
adam says he has some uncommitted code on this. any reason i
shouldn't just add the ./configure option in the meantime?
after the recent flurry of mails with joey/moritz at team at s.d.o, it
seems that it'd be a good idea to have a solid definition of what
kinds of configurations will and will-not be supported for security
updates. specifically, the security team will have nothing to do
with safe_mode/open_basedir type stuff, nor will they fix what are
"application errors" in the php engine. i have a text blurb that i
ran by them that they were happy with, i'll try to dig it up.
- wiki page
it might also be nice to have something set up at
http://wiki.debian.org/php with some really basic info about
the packaging, our group, etc, and make it clear that post-etch users
could post any errata there to supplement bug reports and perhaps
serve as a user-maintained HOWTO/FAQ or something.
when i was helping push forward the php policy draft a year or so ago,
the issue of coinstallability came up. any reason we can't do this?
- other ideas?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-php-maint/attachments/20060919/19b50c44/attachment.pgp
More information about the pkg-php-maint