You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Norman Maurer <no...@apache.org> on 2010/05/01 18:46:46 UTC
[VOTE] Release apache-mailet 2.5
Hi all,
to be able to release James Server 3.0-M1 we need to cut a release of
apache-maile, to remove SNAPSHOT dependencies. So I start a vote for
do so..
So please review and cast your vote:
https://repository.apache.org/content/repositories/orgapachejames-042/
[ ] +1 Please release the artifacts
[ ] +0 No time for review
[ ] -1 Something is wrong or we are not ready for a milestone yet.
Bye,
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release apache-mailet 2.5
Posted by Norman Maurer <no...@apache.org>.
Good point... You are right let us cancel the vote and move the
Interface over.....
Thx for your comments!
Bye
Norman
2010/5/2, Stefano Bagnara <io...@bago.org>:
> 2010/5/1 Stefano Bagnara <io...@bago.org>:
>>> We added support for chaining matchers. See:
>>>
>>> https://issues.apache.org/jira/browse/JAMES-948
>>>
>>> I should prolly add it to mailet jira too..
>>
>> I currently don't understand why this required changes to the mailet
>> api, but maybe I'll understand once I'll be back home and I'll review
>> the sources!
>> I'd expect the matcher composition to be an implementation specific
>> feature and not an API stuff, but I'm probably missing something ;-)
>
> OK, I found the time for reviewing. My opinion is that it would be
> better to have CompositeMatcher in org.apache.james.transport as an
> implementation specific interface at this time and not to alter the
> mailet api with a new interface. The way matchers are
> combined/combinable in a particular mailet container implementation
> should be implementation specific and not defined by the API. An
> implementation could define a DSL to create a complex matcher/mailet
> workflow.
>
> Also, moving the interface to james instead of mailet api allow to
> still depend on the previous mailet-api release (2.4).
>
> So, +0 from me as I don't think we need a 2.5 release that require
> people to recompile their in-house mailet (IIUC we also removed a
> method from mailet api) and doesn't add much in exchange, but I also
> don't want to stop/slow this much needed milestone release effort, so
> if you think 2.5 is the way to go and you don't collect more +1 I can
> change my vote to +1 (it's better to have a new release with something
> I don't like than no release at all ;-) ).
>
> Stefano
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release apache-mailet 2.5
Posted by Stefano Bagnara <io...@bago.org>.
2010/5/1 Stefano Bagnara <io...@bago.org>:
>> We added support for chaining matchers. See:
>>
>> https://issues.apache.org/jira/browse/JAMES-948
>>
>> I should prolly add it to mailet jira too..
>
> I currently don't understand why this required changes to the mailet
> api, but maybe I'll understand once I'll be back home and I'll review
> the sources!
> I'd expect the matcher composition to be an implementation specific
> feature and not an API stuff, but I'm probably missing something ;-)
OK, I found the time for reviewing. My opinion is that it would be
better to have CompositeMatcher in org.apache.james.transport as an
implementation specific interface at this time and not to alter the
mailet api with a new interface. The way matchers are
combined/combinable in a particular mailet container implementation
should be implementation specific and not defined by the API. An
implementation could define a DSL to create a complex matcher/mailet
workflow.
Also, moving the interface to james instead of mailet api allow to
still depend on the previous mailet-api release (2.4).
So, +0 from me as I don't think we need a 2.5 release that require
people to recompile their in-house mailet (IIUC we also removed a
method from mailet api) and doesn't add much in exchange, but I also
don't want to stop/slow this much needed milestone release effort, so
if you think 2.5 is the way to go and you don't collect more +1 I can
change my vote to +1 (it's better to have a new release with something
I don't like than no release at all ;-) ).
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release apache-mailet 2.5
Posted by Norman Maurer <no...@googlemail.com>.
Thats the change which "touched" the api:
http://svn.apache.org/viewvc?view=revision&revision=910035
Bye,
Norman
2010/5/1 Stefano Bagnara <io...@bago.org>:
>> We added support for chaining matchers. See:
>>
>> https://issues.apache.org/jira/browse/JAMES-948
>>
>> I should prolly add it to mailet jira too..
>
> I currently don't understand why this required changes to the mailet
> api, but maybe I'll understand once I'll be back home and I'll review
> the sources!
> I'd expect the matcher composition to be an implementation specific
> feature and not an API stuff, but I'm probably missing something ;-)
> ...
>
> Stefano
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release apache-mailet 2.5
Posted by Stefano Bagnara <io...@bago.org>.
> We added support for chaining matchers. See:
>
> https://issues.apache.org/jira/browse/JAMES-948
>
> I should prolly add it to mailet jira too..
I currently don't understand why this required changes to the mailet
api, but maybe I'll understand once I'll be back home and I'll review
the sources!
I'd expect the matcher composition to be an implementation specific
feature and not an API stuff, but I'm probably missing something ;-)
...
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release apache-mailet 2.5
Posted by Norman Maurer <no...@googlemail.com>.
We added support for chaining matchers. See:
https://issues.apache.org/jira/browse/JAMES-948
I should prolly add it to mailet jira too..
Bye,
Norman
2010/5/1 Stefano Bagnara <io...@bago.org>:
>> to be able to release James Server 3.0-M1 we need to cut a release of
>> apache-maile, to remove SNAPSHOT dependencies.
>
> I don't have repository access right now, what are the changes since
> mailet-api 2.4?
>
> Stefano
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release apache-mailet 2.5
Posted by Stefano Bagnara <io...@bago.org>.
> to be able to release James Server 3.0-M1 we need to cut a release of
> apache-maile, to remove SNAPSHOT dependencies.
I don't have repository access right now, what are the changes since
mailet-api 2.4?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release apache-mailet 2.5
Posted by Vincenzo Gianferrari Pini <vi...@gocloud.it>.
[X] +0 No time for review
Sorry for not being helpful.
Ciao,
Vincenzo
Re: [VOTE] Release apache-mailet 2.5
Posted by Norman Maurer <no...@googlemail.com>.
Hi Robert,
thx for pointing this out.. I think you are right its only minor let
us fix it for the next release and just ignore for now ;)
Bye,
Norman
2010/5/1 Robert Burrell Donkin <ro...@gmail.com>:
> hi norman
>
> there are disclaimers [eg 1] in the poms
>
> IMHO this isn't a major issue and wouldn't stop me +1'ing but since no
> one's voted yet, if you want to reroll, go for it.
>
> - robert
>
> [1]
> | DISCLAIMER DISCLAIMER DISCLAIMER DISCLAIMER DISCLAIMER
> |
> | This file is only intended to be used to build the jsieve
> | website. It must not be used to build packages for jsieve
> | library.
> |
> | DISCLAIMER DISCLAIMER DISCLAIMER DISCLAIMER DISCLAIMER
>
>
> On Sat, May 1, 2010 at 5:46 PM, Norman Maurer <no...@apache.org> wrote:
>> Hi all,
>>
>> to be able to release James Server 3.0-M1 we need to cut a release of
>> apache-maile, to remove SNAPSHOT dependencies. So I start a vote for
>> do so..
>>
>> So please review and cast your vote:
>>
>> https://repository.apache.org/content/repositories/orgapachejames-042/
>>
>> [ ] +1 Please release the artifacts
>> [ ] +0 No time for review
>> [ ] -1 Something is wrong or we are not ready for a milestone yet.
>>
>>
>> Bye,
>> Norman
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-dev-help@james.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [VOTE] Release apache-mailet 2.5
Posted by Robert Burrell Donkin <ro...@gmail.com>.
hi norman
there are disclaimers [eg 1] in the poms
IMHO this isn't a major issue and wouldn't stop me +1'ing but since no
one's voted yet, if you want to reroll, go for it.
- robert
[1]
| DISCLAIMER DISCLAIMER DISCLAIMER DISCLAIMER DISCLAIMER
|
| This file is only intended to be used to build the jsieve
| website. It must not be used to build packages for jsieve
| library.
|
| DISCLAIMER DISCLAIMER DISCLAIMER DISCLAIMER DISCLAIMER
On Sat, May 1, 2010 at 5:46 PM, Norman Maurer <no...@apache.org> wrote:
> Hi all,
>
> to be able to release James Server 3.0-M1 we need to cut a release of
> apache-maile, to remove SNAPSHOT dependencies. So I start a vote for
> do so..
>
> So please review and cast your vote:
>
> https://repository.apache.org/content/repositories/orgapachejames-042/
>
> [ ] +1 Please release the artifacts
> [ ] +0 No time for review
> [ ] -1 Something is wrong or we are not ready for a milestone yet.
>
>
> Bye,
> Norman
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org