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 Stefano Bagnara <ap...@bago.org> on 2006/06/23 00:28:07 UTC

"votes" for next 2.3 release

I hope we don't need a single vote for every single issue, so please 
help with short and clear "vote like" answers to the points (I prefer a 
clear -1 than a long discussion: at least with a -1 we don't delay the 
next release).

--- Add a default hardcoded configuration for the SMTPHandlerChain
http://issues.apache.org/jira/browse/JAMES-496

+1 to apply it
(I would also like to remove the default handlerchain configuration from 
the default config.xml and maybe add it to a commented complete config.xml)

--- Decide what to do with repository implementations configured by 
default (db/dbfile/file)
http://issues.apache.org/jira/browse/JAMES-536

I think we should put dbfile by default in the advanced config, but use 
db or file by default in the default config.xml. I have no real 
preference between the 2. I use db, but I think that most "first time" 
users would better understand the file repositories.

--- Remove RepositoryManager and cornerstone-store-impl
http://issues.apache.org/jira/browse/JAMES-515

+1 to remove it (backport the trunk change)
(Bernd already replied against this, but it is not clear to me wether it 
was a -0 or a -1, so please cast a veto if you think it is needed, 
otherwise we can count the votes: please don't answer that we should 
decide the real plan because I don't believe we can actively discuss 
about what is alpha/beta/rc and what should teoretically be included in 
the branch. I really prefear e real vote on a real issue. We don't have 
a generic rule but at least we know if we agreed to include it or not).

--- Functionality of DNSServer.getByName(String) is not symetric to 
java.net.InetAddress.getByName(String)
http://issues.apache.org/jira/browse/JAMES-302

I would like to move this out from the 2.3 roadmap (2.4). We'll discuss 
wether to include this or not in 2.4/3.0 later.

--- Once we'll have decided what to include and included it we are ready 
for the next release. Do we want to call it 2.3.0b2 or 2.3.0rc1 ?

here is my vote:
+1 for 2.3.0b2
+0 for 2.3.0rc1


Stefano


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


Re: "votes" for next 2.3 release

Posted by Bernd Fondermann <bf...@brainlounge.de>.
A release is overdue, releasing means to finalize and closing issues, 
not to open up new issues on branch2.3. It is not clear to me, what 
branch2.3 is all about anyway, if not applying only bug fixes and 
releasing betas and RCs from it.

Is this something like a last call or intended to go on forever, 
eventually releasing never anything?

I would recommend to first apply patches against TRUNK and merge with 
branch2.3 only when they appear to be stable.

more inline...

Stefano Bagnara wrote:
> I hope we don't need a single vote for every single issue, so please 
> help with short and clear "vote like" answers to the points (I prefer a 
> clear -1 than a long discussion: at least with a -1 we don't delay the 
> next release).
> 
> --- Add a default hardcoded configuration for the SMTPHandlerChain
> http://issues.apache.org/jira/browse/JAMES-496
> 
> +1 to apply it
> (I would also like to remove the default handlerchain configuration from 
> the default config.xml and maybe add it to a commented complete config.xml)

-0 (appears to be a large patch and no bugfix)

> 
> --- Decide what to do with repository implementations configured by 
> default (db/dbfile/file)
> http://issues.apache.org/jira/browse/JAMES-536
> 
> I think we should put dbfile by default in the advanced config, but use 
> db or file by default in the default config.xml. I have no real 
> preference between the 2. I use db, but I think that most "first time" 
> users would better understand the file repositories.

+1 for FILE

> 
> --- Remove RepositoryManager and cornerstone-store-impl
> http://issues.apache.org/jira/browse/JAMES-515
> 
> +1 to remove it (backport the trunk change)
> (Bernd already replied against this, but it is not clear to me wether it 
> was a -0 or a -1, so please cast a veto if you think it is needed, 
> otherwise we can count the votes: please don't answer that we should 
> decide the real plan because I don't believe we can actively discuss 
> about what is alpha/beta/rc and what should teoretically be included in 
> the branch. I really prefear e real vote on a real issue. We don't have 
> a generic rule but at least we know if we agreed to include it or not).

-0 (is a clean up and thus is no improvement for code due to be released)

> 
> --- Functionality of DNSServer.getByName(String) is not symetric to 
> java.net.InetAddress.getByName(String)
> http://issues.apache.org/jira/browse/JAMES-302
> 
> I would like to move this out from the 2.3 roadmap (2.4). We'll discuss 
> wether to include this or not in 2.4/3.0 later.

+1

> 
> --- Once we'll have decided what to include and included it we are ready 
> for the next release. Do we want to call it 2.3.0b2 or 2.3.0rc1 ?
> 
> here is my vote:
> +1 for 2.3.0b2
> +0 for 2.3.0rc1

+1 for b2, if JAMES-496 and -515 are applied to branch2.3
+1 for rc1, if JAMES-496 and -515 are not applied to branch2.3

   Bernd

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


Re: "votes" for next 2.3 release

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

Stefano Bagnara wrote:

>
> --- Add a default hardcoded configuration for the SMTPHandlerChain
> http://issues.apache.org/jira/browse/JAMES-496
>
>
+1 to apply

>
> --- Decide what to do with repository implementations configured by 
> default (db/dbfile/file)
> http://issues.apache.org/jira/browse/JAMES-536
>
>
+1 for file

>
> --- Remove RepositoryManager and cornerstone-store-impl
> http://issues.apache.org/jira/browse/JAMES-515
>
>
-1 to do the removal from branches/v2.3, as, if I understood well, this 
is purely a cleanup that doesn't fix anything, and that could instead 
potentially introduce new problems in the short term. Let's have it in 
trunk ready for 2.4 or whatever will come after 2.3.

>
> --- Functionality of DNSServer.getByName(String) is not symetric to 
> java.net.InetAddress.getByName(String)
> http://issues.apache.org/jira/browse/JAMES-302
>
>
+1 to move this out from the 2.3 roadmap

>
> --- Once we'll have decided what to include and included it we are 
> ready for the next release. Do we want to call it 2.3.0b2 or 2.3.0rc1 ?
>
>
+1 for 2.3.0b2

Vincenzo

>

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


Re: "votes" for next 2.3 release

Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
> Noel J. Bergman wrote:
> 
>> Stefano Bagnara wrote:
>>> I think we should update derby both in trunk and branch, test it works,
>>> and we are ready for the 2.3.0b2 vote.
> 
>> Built, signed and upload in process to
> http://people.apache.org/~noel/james
> 
> Done.
> 
> 	--- Noel

I'm ready to update our site repository with introducing the new docs 
from trunk.

I changed the "documentation" menu to include this items:

James 2.1-2.2 (Old James 2.X)
Design 2.1-2.2 (Old Design)
James 2.3
Design 2.3

I think that for a while we should keep both because:
- many people we'll look for 2.2 even after 2.3 release
- search engines have 2.2 items indexed
- 2.3 docs are not completed yet, but they are better than nothing.

Should I commit it to the site repository and update the minotaur checkout?

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.0b2 Release (Was: "votes" for next 2.3 release)

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

Tomorrow (Saturday) I'll put it in my real production system (file 
repositories only) and watch carefully for one week.

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.0b2 Release (Was: "votes" for next 2.3 release)

Posted by "Noel J. Bergman" <no...@devtech.com>.
> I saw that derby is initialized anyway so I just committed a change to
> 2.3 branch to comment the jdbc embedded driver configuration (also
> updating the default documenting comment).

I'll re-roll the release with that change, and tag it.

+1 from me to release, and I'll look to get it running on my server.  I had
made the configuration changes on the flight, but will have to do them again
since we have changed config.xml again.

	--- Noel


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


[VOTE] James 2.3.0b2 Release (Was: "votes" for next 2.3 release)

Posted by Stefano Bagnara <ap...@bago.org>.
Ok, downloaded and run a simple test. Seems to work.

I saw that derby is initialized anyway so I just committed a change to 
2.3 branch to comment the jdbc embedded driver configuration (also 
updating the default documenting comment).

Btw I think this should not be blocking, and I'm +1 for 2.3.0b2 release.

+1 Stefano Bagnara

Stefano

PS: I updated JIRA to include a 2.3.0b2 release package and its changelog.

Noel J. Bergman wrote:
> Noel J. Bergman wrote:
> 
>> Stefano Bagnara wrote:
>>> I think we should update derby both in trunk and branch, test it works,
>>> and we are ready for the 2.3.0b2 vote.
> 
>> Built, signed and upload in process to
> http://people.apache.org/~noel/james
> 
> Done.
> 
> 	--- Noel


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


Re: "votes" for next 2.3 release

Posted by Norman Maurer <nm...@byteaction.de>.
+1 for update

bye
Norman

Am Donnerstag, den 06.07.2006, 17:51 +0200 schrieb Stefano Bagnara:
> Noel J. Bergman wrote:
> > Noel J. Bergman wrote:
> > 
> >> Stefano Bagnara wrote:
> >>> I think we should update derby both in trunk and branch, test it works,
> >>> and we are ready for the 2.3.0b2 vote.
> > 
> >> Built, signed and upload in process to
> > http://people.apache.org/~noel/james
> > 
> > Done.
> > 
> > 	--- Noel
> 
> I'm ready to update our site repository with introducing the new docs 
> from trunk.
> 
> I changed the "documentation" menu to include this items:
> 
> James 2.1-2.2 (Old James 2.X)
> Design 2.1-2.2 (Old Design)
> James 2.3
> Design 2.3
> 
> I think that for a while we should keep both because:
> - many people we'll look for 2.2 even after 2.3 release
> - search engines have 2.2 items indexed
> - 2.3 docs are not completed yet, but they are better than nothing.
> 
> Should I commit it to the site repository and update the minotaur checkout?
> 
> Stefano
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
> 
> !EXCUBATOR:1,44ad320648531916010323!

RE: "votes" for next 2.3 release

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

> Stefano Bagnara wrote:
> > I think we should update derby both in trunk and branch, test it works,
> > and we are ready for the 2.3.0b2 vote.

> Built, signed and upload in process to
http://people.apache.org/~noel/james

Done.

	--- Noel


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


RE: "votes" for next 2.3 release

Posted by "Noel J. Bergman" <no...@devtech.com>.
Stefano Bagnara wrote:
> I think we should update derby both in trunk and branch, test it works,
> and we are ready for the 2.3.0b2 vote.

Built, signed and upload in process to http://people.apache.org/~noel/james

	--- Noel

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


RE: "votes" for next 2.3 release

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

> Noel J. Bergman wrote:
> > Bernd Fondermann wrote:
> > > I am currently preparing the downloads... please stay tuned.
> > I already did!  Days ago.  And posted them.  And have been waiting for
> > anyone to comment.
> I voted against that release (-0) because of the pending changes we were
> discussing and I applied today. I've not vetoed but no one else voted +1
> so I think we should move forward and try a further vote with the
> updated branch.

Yes, no one else voted.  And it seems that Norman and I were both updating
the Derby libraries.

> I think we should update derby both in trunk and branch, test it works,
> and we are ready for the 2.3.0b2 vote.

Yes.

	--- Noel


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


Re: "votes" for next 2.3 release

Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
> Bernd Fondermann wrote:
> 
>> I am currently preparing the downloads... please stay tuned.
> 
> I already did!  Days ago.  And posted them.  And have been waiting for
> anyone to comment.
> 
> 	--- Noel

I voted against that release (-0) because of the pending changes we were 
discussing and I applied today. I've not vetoed but no one else voted +1 
so I think we should move forward and try a further vote with the 
updated branch.

Norman is upgrading Derby now. I think we should update derby both in 
trunk and branch, test it works, and we are ready for the 2.3.0b2 vote.

Stefano


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


RE: "votes" for next 2.3 release

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

> Bernd Fondermann wrote:
> > I am currently preparing the downloads... please stay tuned.
> I already did!  Days ago.  And posted them.  And have been waiting for
> anyone to comment.

OK, I'll go grab the new Derby and post a new set of builds, including also
the today's set of changes from Stefano.

	--- Noel


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


RE: "votes" for next 2.3 release

Posted by "Noel J. Bergman" <no...@devtech.com>.
Bernd Fondermann wrote:

> I am currently preparing the downloads... please stay tuned.

I already did!  Days ago.  And posted them.  And have been waiting for
anyone to comment.

	--- Noel


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


Re: "votes" for next 2.3 release

Posted by Bernd Fondermann <bf...@brainlounge.de>.
I am currently preparing the downloads... please stay tuned.

   Bernd

Stefano Bagnara wrote:
>> I think we have to stick to 2.3.0b2 because 2.3.0rc1 has a -1.
> 
> 
> I think/hope we'll vote for 2.3.0b2 soon.
> 
> 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: "votes" for next 2.3 release

Posted by Stefano Bagnara <ap...@bago.org>.
Here are the results:

Stefano Bagnara wrote:
> A summary of this week:
> 
> Stefano Bagnara wrote:
>> I hope we don't need a single vote for every single issue, so please 
>> help with short and clear "vote like" answers to the points (I prefer 
>> a clear -1 than a long discussion: at least with a -1 we don't delay 
>> the next release).
>>
>> --- Add a default hardcoded configuration for the SMTPHandlerChain
>> http://issues.apache.org/jira/browse/JAMES-496
>>
>> (I would also like to remove the default handlerchain configuration 
>> from the default config.xml and maybe add it to a commented complete 
>> config.xml)
> 
> 3 +1 Stefano, Norman, Vincenzo
> 1 -0 Bernd
> 
> if no other votes in few days I'll backport it.

Applied to 2.3.
Moved handlerchain configuration to james-smtphandlerchain.xml and 
commented out by default.

>> --- Decide what to do with repository implementations configured by 
>> default (db/dbfile/file)
>> http://issues.apache.org/jira/browse/JAMES-536
>>
>> I think we should put dbfile by default in the advanced config, but 
>> use db or file by default in the default config.xml. I have no real 
>> preference between the 2. I use db, but I think that most "first time" 
>> users would better understand the file repositories.
> 
> db:
> 2 +1 Stefano, Norman
> 
> file:
> 3 +1 Stefano, Vincenzo, Bernd
> 
> dbfile:
> 
> if no one else raise his voice on this issue we should change the 
> default to "file" for users and mail repository.

Moved to file by Norman.

>> --- Remove RepositoryManager and cornerstone-store-impl
>> http://issues.apache.org/jira/browse/JAMES-515
>>
>> +1 to remove it (backport the trunk change)
>> (Bernd already replied against this, but it is not clear to me wether 
>> it was a -0 or a -1, so please cast a veto if you think it is needed, 
>> otherwise we can count the votes: please don't answer that we should 
>> decide the real plan because I don't believe we can actively discuss 
>> about what is alpha/beta/rc and what should teoretically be included 
>> in the branch. I really prefear e real vote on a real issue. We don't 
>> have a generic rule but at least we know if we agreed to include it or 
>> not).
> 
> +1 Stefano, Norman
> -0 Bernd
> -1 Vincenzo *VETO*
> This doesn't need more votes, I just removed this issue from our 2.3 
> roadmap.

Vetoed. Files have been kept.

>> --- Functionality of DNSServer.getByName(String) is not symetric to 
>> java.net.InetAddress.getByName(String)
>> http://issues.apache.org/jira/browse/JAMES-302
>>
>> I would like to move this out from the 2.3 roadmap (2.4). We'll 
>> discuss wether to include this or not in 2.4/3.0 later.
> 
> 4 +1 Stefano, Norman, Vincenzo, Bernd (WOW, the same for all ;-) )
> Updated JIRA (removed from the 2.3 roadmap)

Done.

>> --- Once we'll have decided what to include and included it we are 
>> ready for the next release. Do we want to call it 2.3.0b2 or 2.3.0rc1 ?
>>
>> here is my vote:
>> +1 for 2.3.0b2
>> +0 for 2.3.0rc1
> 
> 2.3.0b2
> 3 +1 Stefano, Norman, Vincenzo
> 1 +1 Bernd (if we include JAMES-496)
> 
> 2.3.0rc1
> +1 Stefano
> +1 Bernd (if we don't include JAMES-496)
> -1 Norman
> 
> I think we have to stick to 2.3.0b2 because 2.3.0rc1 has a -1.

I think/hope we'll vote for 2.3.0b2 soon.

Stefano


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


Re: "votes" for next 2.3 release

Posted by Stefano Bagnara <ap...@bago.org>.
A summary of this week:

Stefano Bagnara wrote:
> I hope we don't need a single vote for every single issue, so please 
> help with short and clear "vote like" answers to the points (I prefer a 
> clear -1 than a long discussion: at least with a -1 we don't delay the 
> next release).
> 
> --- Add a default hardcoded configuration for the SMTPHandlerChain
> http://issues.apache.org/jira/browse/JAMES-496
> 
> (I would also like to remove the default handlerchain configuration from 
> the default config.xml and maybe add it to a commented complete config.xml)

3 +1 Stefano, Norman, Vincenzo
1 -0 Bernd

if no other votes in few days I'll backport it.

> --- Decide what to do with repository implementations configured by 
> default (db/dbfile/file)
> http://issues.apache.org/jira/browse/JAMES-536
> 
> I think we should put dbfile by default in the advanced config, but use 
> db or file by default in the default config.xml. I have no real 
> preference between the 2. I use db, but I think that most "first time" 
> users would better understand the file repositories.

db:
2 +1 Stefano, Norman

file:
3 +1 Stefano, Vincenzo, Bernd

dbfile:

if no one else raise his voice on this issue we should change the 
default to "file" for users and mail repository.

> --- Remove RepositoryManager and cornerstone-store-impl
> http://issues.apache.org/jira/browse/JAMES-515
> 
> +1 to remove it (backport the trunk change)
> (Bernd already replied against this, but it is not clear to me wether it 
> was a -0 or a -1, so please cast a veto if you think it is needed, 
> otherwise we can count the votes: please don't answer that we should 
> decide the real plan because I don't believe we can actively discuss 
> about what is alpha/beta/rc and what should teoretically be included in 
> the branch. I really prefear e real vote on a real issue. We don't have 
> a generic rule but at least we know if we agreed to include it or not).

+1 Stefano, Norman
-0 Bernd
-1 Vincenzo *VETO*
This doesn't need more votes, I just removed this issue from our 2.3 
roadmap.

> --- Functionality of DNSServer.getByName(String) is not symetric to 
> java.net.InetAddress.getByName(String)
> http://issues.apache.org/jira/browse/JAMES-302
> 
> I would like to move this out from the 2.3 roadmap (2.4). We'll discuss 
> wether to include this or not in 2.4/3.0 later.

4 +1 Stefano, Norman, Vincenzo, Bernd (WOW, the same for all ;-) )
Updated JIRA (removed from the 2.3 roadmap)

> --- Once we'll have decided what to include and included it we are ready 
> for the next release. Do we want to call it 2.3.0b2 or 2.3.0rc1 ?
> 
> here is my vote:
> +1 for 2.3.0b2
> +0 for 2.3.0rc1

2.3.0b2
3 +1 Stefano, Norman, Vincenzo
1 +1 Bernd (if we include JAMES-496)

2.3.0rc1
+1 Stefano
+1 Bernd (if we don't include JAMES-496)
-1 Norman

I think we have to stick to 2.3.0b2 because 2.3.0rc1 has a -1.

Stefano


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


Re: "votes" for next 2.3 release

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

Norman Maurer wrote:

>Am Freitag, den 30.06.2006, 16:29 +0200 schrieb Stefano Bagnara:
>  
>
>>A summary of this week:
>>
>>Stefano Bagnara wrote:
>>    
>>
>>>I hope we don't need a single vote for every single issue, so please 
>>>help with short and clear "vote like" answers to the points (I prefer a 
>>>clear -1 than a long discussion: at least with a -1 we don't delay the 
>>>next release).
>>>
>>>--- Add a default hardcoded configuration for the SMTPHandlerChain
>>>http://issues.apache.org/jira/browse/JAMES-496
>>>
>>>(I would also like to remove the default handlerchain configuration from 
>>>the default config.xml and maybe add it to a commented complete config.xml)
>>>      
>>>
>>3 +1 Stefano, Norman, Vincenzo
>>1 -0 Bernd
>>
>>if no other votes in few days I'll backport it.
>>
>>    
>>
>>>--- Decide what to do with repository implementations configured by 
>>>default (db/dbfile/file)
>>>http://issues.apache.org/jira/browse/JAMES-536
>>>
>>>I think we should put dbfile by default in the advanced config, but use 
>>>db or file by default in the default config.xml. I have no real 
>>>preference between the 2. I use db, but I think that most "first time" 
>>>users would better understand the file repositories.
>>>      
>>>
>>db:
>>2 +1 Stefano, Norman
>>
>>file:
>>3 +1 Stefano, Vincenzo, Bernd
>>
>>dbfile:
>>
>>if no one else raise his voice on this issue we should change the 
>>default to "file" for users and mail repository.
>>    
>>
>
>Ok i changed it to file and closed the issue.
>  
>
>>>--- Remove RepositoryManager and cornerstone-store-impl
>>>http://issues.apache.org/jira/browse/JAMES-515
>>>
>>>+1 to remove it (backport the trunk change)
>>>(Bernd already replied against this, but it is not clear to me wether it 
>>>was a -0 or a -1, so please cast a veto if you think it is needed, 
>>>otherwise we can count the votes: please don't answer that we should 
>>>decide the real plan because I don't believe we can actively discuss 
>>>about what is alpha/beta/rc and what should teoretically be included in 
>>>the branch. I really prefear e real vote on a real issue. We don't have 
>>>a generic rule but at least we know if we agreed to include it or not).
>>>      
>>>
>>+1 Stefano, Norman
>>-0 Bernd
>>-1 Vincenzo *VETO*
>>This doesn't need more votes, I just removed this issue from our 2.3 
>>roadmap.
>>
>>    
>>
>>>--- Functionality of DNSServer.getByName(String) is not symetric to 
>>>java.net.InetAddress.getByName(String)
>>>http://issues.apache.org/jira/browse/JAMES-302
>>>
>>>I would like to move this out from the 2.3 roadmap (2.4). We'll discuss 
>>>wether to include this or not in 2.4/3.0 later.
>>>      
>>>
>>4 +1 Stefano, Norman, Vincenzo, Bernd (WOW, the same for all ;-) )
>>Updated JIRA (removed from the 2.3 roadmap)
>>
>>    
>>
>>>--- Once we'll have decided what to include and included it we are ready 
>>>for the next release. Do we want to call it 2.3.0b2 or 2.3.0rc1 ?
>>>
>>>here is my vote:
>>>+1 for 2.3.0b2
>>>+0 for 2.3.0rc1
>>>      
>>>
>>2.3.0b2
>>3 +1 Stefano, Norman, Vincenzo
>>1 +1 Bernd (if we include JAMES-496)
>>
>>2.3.0rc1
>>+1 Stefano
>>+1 Bernd (if we don't include JAMES-496)
>>-1 Norman
>>
>>I think we have to stick to 2.3.0b2 because 2.3.0rc1 has a -1.
>>    
>>
>I whould like to change it to +1.. after using for a while now.
>  
>
I hope to put the current branch 2.3 in production in the next few days 
and keep an eye on it for a week or so. It should be a good test.

Ciao,

Vincenzo

>  
>
>>Stefano
>>    
>>
>
>bye
>Norman
>
>  
>

Re: "votes" for next 2.3 release

Posted by Norman Maurer <nm...@byteaction.de>.
Am Freitag, den 30.06.2006, 16:29 +0200 schrieb Stefano Bagnara:
> A summary of this week:
> 
> Stefano Bagnara wrote:
> > I hope we don't need a single vote for every single issue, so please 
> > help with short and clear "vote like" answers to the points (I prefer a 
> > clear -1 than a long discussion: at least with a -1 we don't delay the 
> > next release).
> > 
> > --- Add a default hardcoded configuration for the SMTPHandlerChain
> > http://issues.apache.org/jira/browse/JAMES-496
> > 
> > (I would also like to remove the default handlerchain configuration from 
> > the default config.xml and maybe add it to a commented complete config.xml)
> 
> 3 +1 Stefano, Norman, Vincenzo
> 1 -0 Bernd
> 
> if no other votes in few days I'll backport it.
> 
> > --- Decide what to do with repository implementations configured by 
> > default (db/dbfile/file)
> > http://issues.apache.org/jira/browse/JAMES-536
> > 
> > I think we should put dbfile by default in the advanced config, but use 
> > db or file by default in the default config.xml. I have no real 
> > preference between the 2. I use db, but I think that most "first time" 
> > users would better understand the file repositories.
> 
> db:
> 2 +1 Stefano, Norman
> 
> file:
> 3 +1 Stefano, Vincenzo, Bernd
> 
> dbfile:
> 
> if no one else raise his voice on this issue we should change the 
> default to "file" for users and mail repository.

Ok i changed it to file and closed the issue.
> 
> > --- Remove RepositoryManager and cornerstone-store-impl
> > http://issues.apache.org/jira/browse/JAMES-515
> > 
> > +1 to remove it (backport the trunk change)
> > (Bernd already replied against this, but it is not clear to me wether it 
> > was a -0 or a -1, so please cast a veto if you think it is needed, 
> > otherwise we can count the votes: please don't answer that we should 
> > decide the real plan because I don't believe we can actively discuss 
> > about what is alpha/beta/rc and what should teoretically be included in 
> > the branch. I really prefear e real vote on a real issue. We don't have 
> > a generic rule but at least we know if we agreed to include it or not).
> 
> +1 Stefano, Norman
> -0 Bernd
> -1 Vincenzo *VETO*
> This doesn't need more votes, I just removed this issue from our 2.3 
> roadmap.
> 
> > --- Functionality of DNSServer.getByName(String) is not symetric to 
> > java.net.InetAddress.getByName(String)
> > http://issues.apache.org/jira/browse/JAMES-302
> > 
> > I would like to move this out from the 2.3 roadmap (2.4). We'll discuss 
> > wether to include this or not in 2.4/3.0 later.
> 
> 4 +1 Stefano, Norman, Vincenzo, Bernd (WOW, the same for all ;-) )
> Updated JIRA (removed from the 2.3 roadmap)
> 
> > --- Once we'll have decided what to include and included it we are ready 
> > for the next release. Do we want to call it 2.3.0b2 or 2.3.0rc1 ?
> > 
> > here is my vote:
> > +1 for 2.3.0b2
> > +0 for 2.3.0rc1
> 
> 2.3.0b2
> 3 +1 Stefano, Norman, Vincenzo
> 1 +1 Bernd (if we include JAMES-496)
> 
> 2.3.0rc1
> +1 Stefano
> +1 Bernd (if we don't include JAMES-496)
> -1 Norman
> 
> I think we have to stick to 2.3.0b2 because 2.3.0rc1 has a -1.
I whould like to change it to +1.. after using for a while now.

> 
> Stefano

bye
Norman