Because I wamt to push 1.6.0 as soon as possible. When I now start to work on imap in trunk we have some half done work again which will just block the release...
bye, norman Von meinem iPad gesendet Am 24.12.2011 um 09:55 schrieb Eric Charles <[email protected]>: > +1, IMAP's home is Protocols. > > Why not directly move IMAP in Protocols' trunk and let it evolve at its own > pace? Close integration can take time, but at least it will be at its place. > > Eric > > On 23/12/11 09:14, Stefano Bagnara wrote: >> 2011/12/23 Norman Maurer<[email protected]>: >>> Hi there, >>> >>> as I have some spare time next week (at least it seems like that at moment >>> but who knows ;)) I want to start an experiment. I want to try to merge the >>> imap code base into the protocols project as module. I think this makes a >>> lot of sense, as our protocols api should be flexible enough for this. >>> Beside this all other protocol implementations are in there like POP3, SMTP >>> and LMTP. So adding IMAP would by just make sense ;) >>> >>> For this I will create a branch and work in there as I'm almost sure it >>> will need some love and I don't want to mess with it in trunk now that we >>> are so close to 1.6.0 release in Protocols. Once the merge is done and >>> works I plan to cut a 2.0 release as I expect to need some api changes too. >>> If we don't need api changes we can just release it as 1.7.0. >>> >>> Any comments ? >> >> +1 >> >> It sounds really interesting! >> >> Stefano >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > -- > Eric http://about.echarles.net > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
