Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: transition Hi, we currently have PostgreSQL 9.3 in unstable/testing. PostgreSQL 9.4.0 will be releasing around September. 9.4~beta1 is already in experimental, and 9.4~beta2 will release next Thursday. Our plan is to upload this beta2 of postgresql-9.4 to unstable, and set the 9.4 as the only supported PostgreSQL version as per /usr/share/postgresql-common/supported-versions. postgresql-9.3 will stay in unstable (and testing) until all dependencies have been moved to 9.4. This is mostly just recompiling the extension module packages; most will adjust to the new version automatically. I've tested most of the "interesting" packages, most of them do not have any issues with 9.4. For a handful, fixes have already been made upstream, pending new releases, and some need some trivial debian/ updating. All in all, atm there is only one package (pg-reorg) which I know isn't 9.4-ready, and that's probably just a matter of pinging upstream (TBD). As with the other PostgreSQL server packages, we will provide new minor versions as upstream releases them, so jessie should be releasing with something like 9.4.2, which sounds like a nice target. I believe this transition should only require little (if any) release team attention (no group of packages should need to enter testing in parallel), though of course we'd like your opinion. Does this plan look sane? Ben file: title = "postgresql-9.4"; is_affected = .depends ~ /postgresql.*-9.[34].*/; is_good = .depends ~ /postgresql.*-9.4.*/; is_bad = .depends ~ /postgresql.*-9.3.*/; Christoph -- cb@df7cb.de | http://www.df7cb.de/
Attachment:
signature.asc
Description: Digital signature