and then release something. If others are also tired, I vote that we put out 3.2.0b5 now to show the world that we're back on track, and then put out 3.2.0rc1 when the exhaustive testing is done. That way we may have some feedback from beta testers before RC1 too.
Yep ... I agree. I also don't have much time at the moment to do futher testings. I agree with the fact that doing all testings and releasing RC1 would be the optimal; however if this is not possible (as it seems to be right now), we should freeze the code right now and release immediately a 3.2.0b5 version showing the world that we are moving as Lachlan says.
By doing this, we could get some important feedback (and potentially testings) from users.
So, yes I vote for releasing 3.2.0b5 even next week and delaying 3.2.0-RC1 at the end of november early december.
What do you think guys?
Ciao -Gabriele
--
Gabriele Bartolini: Web Programmer, ht://Dig & IWA/HWG Member, ht://Check maintainer
Current Location: Melbourne, Victoria, Australia
[EMAIL PROTECTED] | http://www.prato.linux.it/~gbartolini | ICQ#129221447
> "Leave every hope, ye who enter!", Dante Alighieri, Divine Comedy, The Inferno
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
