[fetchmail-devel] Gitorious branch reshuffling

[Matthias A. <mat...@gm...>]

Greetings,

I am in the process of changing the branches in the Git repository
around.  I am planning to do 6.3.20 as a last 6.3.X release, to fix
timeouts and collect other accumulated fixes.

6.4.0 will drop some cruft, require - conservatively - a bit more modern
systems (though those compliant to 2001+ standards should be good),
accelerates POP3 and should fix socket timeout handling a bit more
aggressively.

7.0.0 is future work, has started, but requires major overhauls for
maintainability and more radical changes. Likely to diverge from 6.X
to the point that code merges become impossible.


This is the current shape:

-------------------------------------------------------------------------
Git name of     Future     Future
BRANCH		Releases   Directions
-------------------------------------------------------------------------
legacy_63	6.3.X	   to be frozen after 6.3.20, except security
(new)                      or grave bugs, last to support ancient OSes
-------------------------------------------------------------------------
master          6.4.X      feature remove branch, drops SSLv2, IMAP2,
                           POP2, RPOP, and more, speeds up POP3,
                           interim branch for fixes with less ballast,
                           likely the last in C (without C++), requires
                           newer operating system and C compiler
                           (SUSv3 and C89 should do for now, may
                           require C99 soonish).

                           I have back-merged anything not C++-related
                           from the "next" branch.
-------------------------------------------------------------------------
common-6x       none       branch to collect changes shared between
(new)                      legacy_63 and master, "common ancestor"
-------------------------------------------------------------------------
next            7.0.X      development/major overhaul branch,
                           converted to C++, to be rebased onto master
                           soon (if possible, haven't tried)
-------------------------------------------------------------------------

I'll send another notice once the "next" branch has been rebased onto
master, or if I give up on that plan.

Note that those who have pulled from Git in the past few hours may need
to discard the past few changes on upstream/master and re-pull.

Also note that you may need to "make distclean" and re-configure. To
obtain the current ./configure options you'd used, run "./config.status
--version" and look at the first few lines of output.

-- 
Matthias Andree