From: Brian M. <br...@gr...> - 2008-05-05 04:14:10
|
Doug, > I wanted to have some time to test all of the > updates for the 3.0.2 > release that I have made to trunk, and so I didn't > want to risk putting > them all in at the last moment. So, I still have > some changes that *could* > go into the 3.0 branch. > > Will there be a 3.0.3? Should I put them in after > the 3.0.2 is released? > Or should I put them in, and we take a few days to > test? The next release will be 3.0.1, not 3.0.2. I fully expect that there will be a 3.0.2, 3.0.3 and so on in the following months. That's the whole point of the maintenance branch. So if your changes don't make it in this one, it isn't too late for the next release. It is the general expectation of the community that the nature of the changes that go into a maintenance branch are small, explainable, and low risk. This typically means that a lot of testing isn't necessary. If your changes don't fall into that category, then let's please discuss. Otherwise, let us know when you're ready for the release. Thanks for everything! ~Brian |