Hello all, First, thank you to everyone for the show of support in keeping me on for 2.6. A few people did express concern that I might be over-burdened as I continue as the maintainer for 2.5. I think that concern is valid, but I think we can also take a wait-and-see approach to the issue. My brief experience with maintaining 2.5 leads me to believe that packaging a release is more about achieving the necessary focus than about the actual time involved, so it's my hope that handling two releases will give me some economies of scale, so to speak. We shall see, and I won't hesitate to ask for help if needed.
Second, I want to solicit feedback on a preliminary timeline for 2.6. As stated before, I think we will be best served to have an abbreviated release which gets us back on our March/September timeline. With that in mind, here is what I am thinking: alpha (bugs targetted) - Jan. 16 alpha cut - Jan. 21 beta (bugs targetted) - Feb. 4 beta cut - Feb. 11 RC (bugs targetted) - Mar. 4 RC - Mar. 6 Of these dates, the most meaningful is of course the beta cutoff, which would effectively be Feb. 4. I am also scheduling the longest review/commit period for the beta release, since I expect there to be the usual bulge of pullrequests. So, do we collectively think this is doable? If not, what adjustments should we consider? Thanks for your thoughts, Dan
