Starting unstable development, branching for etch

[Fabian Fagerholm]

On Fri, 2007-02-23 at 12:06 -0500, Roberto C. Sanchez wrote:
> I generally don't have much time to mess with unstable.  However, I
> maintain a few of my own backports and so I would like to volunteer to
> lead this effort.

Excellent! :)

I created an etch-backport branch. Feel free to use it to pull stuff
from trunk and make it work on etch. The trunk version is likely to be
completely usable on etch for some time to come, so initially you're
just going to be syncing with the etch branch and trunk, having little
or no changes. At some point, there will be changes that require actual
backporting.

I also suggest merging some of the least intrusive changes into the etch
branch to have something to offer for point releases of etch. That's not
mandatory backporter work, but I presume backporters will have a
reasonable overview of what will work in etch and what won't. All this
while considering current point release policy, of course.

To make the work efficient, do follow the branching and merging advice
in the SVN book:
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.html

Releasing a backport should work as usual with svn-buildpackage. You
create changelog entries with backport-style version numbers, and tag
each release as usual. So the released backport-versions will appear in
the tags directory just as every other released version. At least that's
how it's supposed to work.

Anyway, etch isn't actually out yet, so it will be a while before the
actual backporting work can commence. So there's plenty of time to
grease the tool chain and check that SVN-fu. :)

-- 
Fabian Fagerholm <fabbe at paniq.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20070223/10e3a205/attachment.pgp