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 "Noel J. Bergman" <no...@devtech.com> on 2006/06/02 18:27:31 UTC

[VOTE] James 2.3.0 Beta 1

Tagged and built.  Currently uploading to http:/people.a.o/~noel/james.  It
was built on my new server, so please try to test this on JDK 1.4.2, not
just Java 5.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: [VOTE] James 2.3.0 Beta 1

Posted by Bernd Fondermann <bf...@brainlounge.de>.
+1, release it

Noel J. Bergman wrote:
> Tagged and built.  Currently uploading to http:/people.a.o/~noel/james.  It
> was built on my new server, so please try to test this on JDK 1.4.2, not
> just Java 5.
> 
> 	--- Noel
> 
> 
> ---------------------------------------------------------------------
> 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] James 2.3.0 Beta 1

Posted by Vincenzo Gianferrari Pini <vi...@praxis.it>.
Noel J. Bergman wrote:

>Stefano Bagnara wrote:
>
>  
>
>>James is a top level project and we didn't publish any release
>>versioning scheme, so we can simply vote and do what we voted.
>>    
>>
>
>+1
>
>And I'll be happy to see Vincenzo's code dropped into v2.3 when we release
>it.  The logic I apply is that it is not a core change, but optional
>matchers/mailets, so if there is a bug, there is no risk to most users.
>
>  
>
In fact this was my reasoning: if (unlikely  ;-) ) there is a bug, it 
just can switched off, as it is an added optional functionality whose 
purpose is to reduce the risk of false positives in spam detection.

But I asked because I felt that the "beta" status of v2.3 could have 
raised some perplexity, as it did.

So today or tomorrow I will commit it both in trunk and v2.3.

Vincenzo

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


RE: [VOTE] James 2.3.0 Beta 1

Posted by "Noel J. Bergman" <no...@devtech.com>.
Stefano Bagnara wrote:

> James is a top level project and we didn't publish any release
> versioning scheme, so we can simply vote and do what we voted.

+1

And I'll be happy to see Vincenzo's code dropped into v2.3 when we release
it.  The logic I apply is that it is not a core change, but optional
matchers/mailets, so if there is a bug, there is no risk to most users.

> we make 1 release every 2 years

I'd like that to change, though.  I would not mind seeing a minor release
every two months or so, primarily adding bug fixes, minor improvements, and
matchers/mailets to a major release.  And I would not mind seeing a major
release once or twice per year, so long as we have the new material and it
has been vetted as sufficiently qualitative to stamp our approval on it.

This is why I make an issue about release management.  Not to stop work, but
to try to separate longer term, risky, changes from what can go into the
next near-term release.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: [VOTE] James 2.3.0 Beta 1

Posted by Stefano Bagnara <ap...@bago.org>.
Ahmed Mohombe wrote:
>> Where did you read the "beta" definition by Apache?
> Somewhere on one of the many Apache mailing lists.

Well, James is a top level project and we didn't publish any release 
versioning scheme, so we can simply vote and do what we voted.

AFAIK some apache project has a published release versioning policy but 
noone published the "suffix" policy.

Imho we make 1 release every 2 years, we shouldn't loose too much time 
around version numbering and similar things.

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: [VOTE] James 2.3.0 Beta 1

Posted by Ahmed Mohombe <am...@yahoo.com>.
> Ahmed Mohombe wrote:
>>> Am I still in time to put it in james/server/branches/v2.3 before final?
>> Isn't the idea of "beta" on Apache not to add any feature, only bug 
>> fixes?
>>
>> Ahmed.
> 
> This is my idea of RC.
Nope. RC means that there are only very small bug fixes (glitches at most), i.e.
almost release ready, hence the name "Release Candidate".

> Where did you read the "beta" definition by Apache?
Somewhere on one of the many Apache mailing lists.


Ahmed.


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: [VOTE] James 2.3.0 Beta 1

Posted by Stefano Bagnara <ap...@bago.org>.
Ahmed Mohombe wrote:
>> Am I still in time to put it in james/server/branches/v2.3 before final?
> Isn't the idea of "beta" on Apache not to add any feature, only bug fixes?
> 
> Ahmed.

This is my idea of RC.
Where did you read the "beta" definition by Apache?

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: [VOTE] James 2.3.0 Beta 1

Posted by Ahmed Mohombe <am...@yahoo.com>.
> Am I still in time to put it in james/server/branches/v2.3 before final?
Isn't the idea of "beta" on Apache not to add any feature, only bug fixes?

Ahmed.


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: [VOTE] James 2.3.0 Beta 1

Posted by Stefano Bagnara <ap...@bago.org>.
Vincenzo Gianferrari Pini wrote:
> In the next couple of days I would commit a couple of new mailet/matcher 
> to deal with whitelists, that I've been using successfully in the last 
> couple of years and that are requiring just minor modifications (only 
> sqlResources.xml support).
> 
> Am I still in time to put it in james/server/branches/v2.3 before final?

IMHO you are in time, but I would prefer to see the code in trunk before 
deciding wether we should backport to 2.3 branch or not.

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: [VOTE] James 2.3.0 Beta 1

Posted by Vincenzo Gianferrari Pini <vi...@praxis.it>.
In the next couple of days I would commit a couple of new mailet/matcher 
to deal with whitelists, that I've been using successfully in the last 
couple of years and that are requiring just minor modifications (only 
sqlResources.xml support).

Am I still in time to put it in james/server/branches/v2.3 before final?

Vincenzo

Noel J. Bergman wrote:

>Tagged and built.  Currently uploading to http:/people.a.o/~noel/james.  It
>was built on my new server, so please try to test this on JDK 1.4.2, not
>just Java 5.
>
>	--- Noel
>
>
>---------------------------------------------------------------------
>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] James 2.3.0 Beta 1

Posted by "Noel J. Bergman" <no...@devtech.com>.
Stefano Bagnara wrote:

> the activation.jar bundled seems to be the one from ibiblio
> and not the one from sun.

> I already cast my +1 for the same archive with with replaced
> activation jar from sun, if needed.

I have the new activation.jar from Sun, and will start using it.  Still
working with Sun to get them to fix the incorrect license, since it is
*supposed* to be CDDL, as per
http://wiki.java.net/bin/view/Projects/GlassFishCodeDependencies.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: [VOTE] James 2.3.0 Beta 1

Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
> Tagged and built.  Currently uploading to http:/people.a.o/~noel/james.  It
> was built on my new server, so please try to test this on JDK 1.4.2, not
> just Java 5.
> 
> 	--- Noel

+1: Tested under windows with both 1.5.0 and 1.4.2 with default 
configuration and works.

Like for 2.3.0a3 the activation.jar bundled seems to be the one from 
ibiblio and not the one from sun.

I don't know if you did this by mistake or not: imho this is a beta and 
we can release it anyway.. but you are so "paranoid" about the source of 
the jars that I thought you were interested in it.

I already cast my +1 for the same archive with with replaced activation 
jar from sun, if needed.

Stefano


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Re: [VOTE] James 2.3.0 Beta 1

Posted by Vincenzo Gianferrari Pini <vi...@praxis.it>.
+1
Vincenzo

Noel J. Bergman wrote:

>Tagged and built.  Currently uploading to http:/people.a.o/~noel/james.  It
>was built on my new server, so please try to test this on JDK 1.4.2, not
>just Java 5.
>
>	--- Noel
>
>
>---------------------------------------------------------------------
>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] James 2.3.0 Beta 1

Posted by Norman Maurer <nm...@byteaction.de>.
I don't whould add such new features in the next stable release. I think
we agreed that we called it "feature freezed". I whould add them to the
current trunk where we could test it more (maybe you have test it enough
the last years) and write junit tests if you don't have allready some..

Anyway if the others think we should add them im not against this..

bye
Norman

Am Freitag, den 09.06.2006, 14:33 +0200 schrieb Vincenzo Gianferrari
Pini:
> In the next couple of days I would commit a couple of new mailet/matcher 
> to deal with whitelists, that I've been using successfully in the last 
> couple of years and that are requiring just minor modifications (only 
> sqlResources.xml support).
> 
> Am I still in time to put it in james/server/branches/v2.3 before final?
> 
> Vincenzo
> 
> Noel J. Bergman wrote:
> 
> >Tagged and built.  Currently uploading to http:/people.a.o/~noel/james.  It
> >was built on my new server, so please try to test this on JDK 1.4.2, not
> >just Java 5.
> >
> >	--- Noel
> >
> >
> >---------------------------------------------------------------------
> >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
> 
> !EXCUBATOR:1,44896cc137027091824328!