On Mon, 2012-06-04 at 08:55 +0200, Milan Crha wrote:
> What about a "compromise", drop support for evolution-exchange when
> 3.7.x development begins? I suppose it'll be fair to have the main API
> changes done and any potential community person taking care of it will
> not need to learn all the ha
On Fri, 2012-06-01 at 15:48 -0400, Matthew Barnes wrote:
> The backend-facing APIs less so. They tend to see more churn anyway,
> even without my branch. I can't think of a recent release where the
> backend APIs didn't change a little. And that's fine -- the damage is
> contained -- but we stil
On Fri, 2012-06-01 at 19:49 +0200, Milan Crha wrote:
> evolution-ews
>- for 2007,2010 servers (through https, with simpler dependencies)
>- it's currently semi-maintained
>- note the EWS implementation on Exchange servers is not feature
> complete on 2007 servers (I read/saw some a
On Fri, 2012-06-01 at 06:57 -0400, Matthew Barnes wrote:
> On Fri, 2012-06-01 at 15:19 +0530, Chenthill wrote:
> > Then why not retire evolution-mapi instead of evolution-exchange ?
>
> I hadn't considered that. I'll defer to Milan to make that call.
>
> I thought evolution-mapi worked with Exch
On Fri, 2012-06-01 at 08:39 -0600, Vibha Yadav wrote:
> > On Fri, 2012-06-01 at 15:19 +0530, Chenthill wrote:
> I can provide you the support. I will be getting into the new project
> coming Monday. I can keep myself involved during free time after a
> couple of weeks time..
> I can also contribu
Thanks & Regards,
Vibha
>>> Chenthill 6/1/2012 4:37 PM >>>
On Fri, 2012-06-01 at 06:57 -0400, Matthew Barnes wrote:
> On Fri, 2012-06-01 at 15:19 +0530, Chenthill wrote:
> > Then why not retire evolution-mapi instead of evolution-exchange ?
>
> I hadn't considered that. I'll defer to Milan to
On Fri, 2012-06-01 at 15:19 +0530, Chenthill wrote:
> W.r.t evolution-groupwise, it would be good to continue it until this
> release.
Sorry, I read "this release" to mean 3.6. If you just meant 3.5.2 then
I guess disregard my other response. Haven't had my coffee yet. :)
_
On Fri, 2012-06-01 at 06:57 -0400, Matthew Barnes wrote:
> On Fri, 2012-06-01 at 15:19 +0530, Chenthill wrote:
> > Then why not retire evolution-mapi instead of evolution-exchange ?
>
> I hadn't considered that. I'll defer to Milan to make that call.
>
> I thought evolution-mapi worked with Exch
On Fri, 2012-06-01 at 15:19 +0530, Chenthill wrote:
> Then why not retire evolution-mapi instead of evolution-exchange ?
I hadn't considered that. I'll defer to Milan to make that call.
I thought evolution-mapi worked with Exchange 2003 servers at least in
theory; I don't know how much actual te
On Thu, 2012-05-24 at 16:15 -0400, Matthew Barnes wrote:
> The release of Evolution-ActiveSync brings the number of Evolution Data
> Server backend modules for Microsoft Exchange up to four.
>
> Even if we had the manpower to adequately maintain all these, which we
> don't, four different backends
On Thu, 2012-05-31 at 23:19 -0600, Akhil Laddha wrote:
> > I'm adding Evolution-GroupWise to the retiree list, since it no longer
> > has any active maintainers.
Urk; I'm an active user too ...
> There were some good amount of changes in groupwise source code post
> 3.5.1 release. These
On Thu, 2012-05-31 at 15:54 -0400, Matthew Barnes wrote:
> I'm adding Evolution-GroupWise to the retiree list, since it no longer
> has any active maintainers.
>
> Haven't heard any objections so I take that to mean consent from the
> rest of the team. I don't plan to release any more 3.5 tarba
On Thu, 2012-05-24 at 16:15 -0400, Matthew Barnes wrote:
> Therefore I think it's time to retire Evolution-Exchange. That module
> has seen steadily decreasing maintenance for several years, the newest
> version of Exchange it supports is now a decade old, and frankly it was
> never all that relia
On Thu, 2012-05-24 at 16:15 -0400, Matthew Barnes wrote:
> The release of Evolution-ActiveSync brings the number of Evolution Data
> Server backend modules for Microsoft Exchange up to four.
>
> Even if we had the manpower to adequately maintain all these, which we
> don't, four different backends
14 matches
Mail list logo
