Any reason not to move forward now? (time permitting, of course :)
Things seem to be ok at the moment... I'm using the current trunk and
did a whole lot of building without a local repo with a mix of new
and existing artifacts yesterday without issues (other than one or
two non-blocking
I say do it now, and start the vote now.
I've got a security related issue I'm working on now.
But I'd like to vet that for the 1.0-beta-4 release, not this 1.0-beta-3
release.
- Joakim
Brett Porter wrote:
Any reason not to move forward now? (time permitting, of course :)
Things seem to be
On 10/25/07, Maria Odea Ching [EMAIL PROTECTED] wrote:
These are the results of the vote:
+3 Binding votes (Fabrice, Brett and Myself)
-1 Binding vote (Arnaud)
+2 Non-binding votes (James, Olivier)
With all the regressions that were discovered in 1.0-beta-3, it seems
that it would be
These are the results of the vote:
+3 Binding votes (Fabrice, Brett and Myself)
-1 Binding vote (Arnaud)
+2 Non-binding votes (James, Olivier)
With all the regressions that were discovered in 1.0-beta-3, it seems
that it would be better to postpone the release. I will remove the tag
for
