On 18-02-14 00:55, Reindl Harald wrote:
>
>
> Am 18.02.2014 00:44, schrieb Peter Milesson:
>> I have upgraded a mail server from DBMail 3.0.2 to 3.1.10 master branch from
>> 11.02.2014
>
> please define "master branch"
>
> master is that: http://git.dbmail.eu/paul/dbmail/log/, unstable, not for
> production
> 3.1.x is that: http://git.dbmail.eu/paul/dbmail/log/?h=dbmail_3_1
>
> if you really upgraded to *master* your did something terrible wrong
> there may be some commits with the same decription in master and 3.1 tree
> but the 3.1 tree has *backports* with no major changes
> that is a complete different world compared with unstable master
My workflow is slightly different for git-internal reasons:
new features only end up on the master branch.
bug-fixes are done on the dbmail_3_1 branch and afterward forward-ported
to the master branch using git-cherry-pick. The main differences between
dbmail_3_1 and master are:
- new imap capabilities like: literal+ uidplus within condstore qresync
- a lot of small fixes resulting from static analysis using coverity
I assume Peter is using dbmail_3_1 on revision
e89ac73209e0902c0fc4a71e79ea12fe66b22cd8
Using the master branch is indeed for the brave of heart. But I run it
myself to test all the new IMAP capabilities and it's not in bad shape
at all - afaik. But I do mess up a commit now and then...
@Peter, are you running a proxy in front of dbmail? Most problems
reported here on 3.1 were solvable using a proxy like dovecot or nginx.
But I guess it depends on the problems you'll be reporting.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, github, linkedin
www.nfg.nl/[email protected]/+31.85.877.99.97
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
