Axel Thimm wrote:
How about using a version scheme starting with "2.0"? If there is a
pigeonhole for each 2.0.x release, then

dovecot-2.0.x.tar.bz2
dovecot-pigeonhole-2.0.x.tar.bz2

could be the released pairs.
That's the problem. Timo and I do not release new versions synchronously. Only when Timo happens to break Pigeonhole with a Dovecot change, I tend to do a forced release.

Regards,

Stephan.

Reply via email to