On 07/19/2011 10:15 AM, Hyrum K Wright wrote: > Since there seems to be consensus regarding not releasing 1.7.0-beta1, > I'll clean out STATUS and go roll beta2 this afternoon with the hopes > of releasing it by the end of the week. > > I'm half-tempted to call it rc1 and start the soak. Thoughts?
I don't follow the arguments for not releasing beta1, but I'm late to the party and accept the consequences thereof. Still, you can't call it an RC if it's not release-ready. I know that there are some changes that we allow between an RC and final release without restarting the soak (updating CHANGES, for example). But there are still several yellow in-progress items in roadmap.html. Most of them I could probably assign a committer's name to as the person who seemed to be carrying the banner for that task. Is anyone able/willing to review and update the status of those items so we can enter RC1 with a sense of release-readiness? What about ra_serf's "default-ness" -- is it in the appropriate state based on that library's readiness at this moment? -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
