> > As a compromise, I'm proposing to post 2.2.0RC1 *today*. Not next week, the > > week after, or the week after. Post it today with the intent of releasing > > 2.2.0 next Friday if there are no blocking issues. Give everyone one week > > to know that this is intended to be the 2.2.0 Release. This gives everyone > > a chance to synchronize and test THIS build. > > Ok, tag, branch, and post 2.2.0rc1 today 4/16, with an aim to start a > vote and release next Friday 4/23 (so get on mirrors by Monday 4/26). > You want to do this, or should I? I can get to it late tonight.
FWIW, next week I will be traveling abroad and will not be able to even read my mail. So I won't be able to test nor to vote. Vincenzo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
