2.3.16 code drop action?

[Henrique de Moraes Holschuh]

Well, it is not a the state I'd like, but its best I at least commit
something instead of taking more time.  The changelog needs more love, and I
want to clean up more stuff before I even consider putting it forward as a
candidate for an experimental or unstable upload.

I have gone over all the debian patches, and cleaned them up for 2.3.16.  I
will go over them again, many of those need a bit more care, and the ones
which will be thruly useless when I am done with, need to be removed.

And we need to send a lot of that stuff upstream after the clean up.  Bron
wants to use the Debian packages in fastmail.fm, so we can expect some help
in that front with the upstream triaging.

I am also going to revamp that build system.  I have it somewhat cleaned up
already, but it is not done yet so I didn't add it to the code drop.  When I
am done, the build will bootstrap entirely from clean Debian tools, and we
will have an easier time with new upstream code merging.  Oh, and it will
have a README.source, to help everyone :-)

The debian changelog is not fully complete on the drop.  I will fix that in
the next drop.

The tree I am using is based on upstream tarball releases.  I will keep an
eye on the incremental work being done on the other cyrus 2.3 working
branch (no, it is not entirely up-to-date yet).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh