Hi Folks, the Vote is over. As Scott suggested, I will not upgrade the commons-email dependencies. Since there are no objections I will apply lazy consensus and prepare the RC1 Release tomorrow.
One further question. I would like to get rid of the Checkstyle errors as long as they are only a missing space here, and bla schmah there. Should I do that after the Release or do this before the RC2 Release? Kind regards Juergen > -----Ursprüngliche Nachricht----- > Von: Jürgen Hoffmann [mailto:[EMAIL PROTECTED] > Gesendet: Sonntag, 13. April 2008 13:34 > An: 'Turbine Developers List' > Betreff: AW: VOTE to apply Scotts' Patch for updated Libraries > > Hi, > > So if no one is against starting with a Release Candidate until the > deadline of the vote I will assume lazy consensus. > > I will update the changes.xml accordingly. > > Kind regards > > Juergen > > > -----Ursprüngliche Nachricht----- > > Von: Thomas Vandahl [mailto:[EMAIL PROTECTED] > > Gesendet: Sonntag, 13. April 2008 11:48 > > An: Turbine Developers List > > Betreff: Re: VOTE to apply Scotts' Patch for updated Libraries > > > > Jürgen Hoffmann wrote: > > > Hi all, > > > > > > I want the patch to be applied. We have a beta release cycle > started, > > so we should have enough time to get all the problems sorted out that > > the new lib versions might bring. The Vote ends on Wednesday 7 pm > CEST. > > > > > > With this mail I want to extend the vote for the beta 1 release of > > turbine 2.3.3 to the same time. I also want to volunteer as the > release > > manager. So if the vote passes I will apply the patch and release > beta > > 1 afterwards. > > > > > [X] +1 Update versions > > > [ ] +0 go ahead I do not care > > > [ ] -0 I don't care > > > [ ] -1 The updated libraries make current 2.3.2 applications > useless > > > > Actually, I'm a bit hesitant to update dependencies just because they > > are there. I take it that when switching to Maven-2 we will be able > to > > state "works with commons-configuration 1.2 and up"? That would be a > > better solution. However as things are now, it is probably the best > > idea > > to update the stuff. > > > > Please don't forget to add this fact to the changes.xml. (I usually > > forget this...) > > > > Two additional remarks on the release: > > 1. I looked at the list of changes since 2.3.2 and it is fairly long. > > Looks like progress has indeed been made, although slowly. > > > > 2. As discussed with Juergen, I'd rather start with a Release > Candidate > > instead of a beta. I think that the state of the code justifies this. > > > > So Juergen, go ahead. It's good to have you back. If you have any > > questions, feel free to ask. > > > > Bye, Thomas. > > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
