To me it feels like another RC would be best. So many changes went in since RC 1 that feedback and community testing are needed. If things are stable with RC 2 then we can release. There also one non trivial issue/feature I'll ask about ASAP on the ML.
Gary <div>-------- Original message --------</div><div>From: Ralph Goers <ralph.go...@dslextreme.com> </div><div>Date:06/19/2014 00:57 (GMT-05:00) </div><div>To: Log4J Developers List <log4j-dev@logging.apache.org> </div><div>Subject: Next Release </div><div> </div>We are overdue for a release. The only question I have is whether it should be rc2 or GA. 1. Are there any open issues that are blockers to a GA release? 2. Is everyone comfortable with the state of the code for a GA release? For me, I am not aware of any blockers and I think the code is good. The only thing I am wondering is with all the changes that have been made from rc1 what risk there is with this release being GA. I suppose one possibility would be to release rc2 and then do GA after just a few weeks. Thoughts? Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
