Hi Duncan, > 2.3.8 is already in experimental, but incase's cyrus23 SVN branch hasn't > been touched for a year. I'm guessing from the tiny volume of traffic > on the coordination list, and the quietness of the SVN repo that the > team don't have time to update to 2.3.13. We've already done that, and > added a bunch of tweaks and new patches that suit _our_ needs. We'd > love to see a 2.3 package set in official Debian that meets _everyone's_ > needs. We're willing to contribute existing code, people's time, SVN > servers, build hosts, etc, to help that happen. > > How can we best do this? Who else is doing the same things?
How about joining pkg-cyrus-imapd team on alioth? Speaking for myself I have very good experience with drawing new blood into packaging teams. We/I can always sponsor uploads prepared by somebody else. We are of course also interested in people who will look at old bugs and help them fix them, ie. not just put new shiny versions/features. And please bear in mind that we try to be pretty conservative, especially when it comes to bdb version. That also means that before 2.3 hits unstable there has to be a clean way how to upgrade from 2.2 (including all those nasty bdb databases, etc.). Ondrej. P.S.: I am happy running cyrus-imapd 2.2, so there is no strong push to invest time into packaging 2.3 before lenny is out (or arguing on this list whether somebody agree or disagree). But I am willing to support others work. -- Ondřej Surý <ond...@sury.org>
