I think maybe what we'll do in the future is run a more formal beta process.
For example, we'll release the beta announcement, and once we receive 25 responses from people who have tested their applications with the new version, then we'll release... (might take a bit to figure out what the right number should be). In this case it was a simple bug that a unit test could have easily caught, it's just a matter of thinking of the use case... or all use cases. Clinton On Mon, Jul 7, 2008 at 8:33 AM, Tom Duffey <[EMAIL PROTECTED]> wrote: > > On Jul 7, 2008, at 9:15 AM, Clinton Begin wrote: > > What keeps you from testing the Beta versions when we release them? > There's not much point in a beta period if nobody tries them... :-/ > > > I guess it's because in our JIRA the "Upgrade to IBATIS xxx" entry is one > of those rainy day tasks that we get around to when we can. We do have > several large projects using IBATIS, though, so I'll try to pay more > attention to your betas to give you some early feedback. > > Tom > > On Mon, Jul 7, 2008 at 8:05 AM, Tom Duffey <[EMAIL PROTECTED]> wrote: > >> Hi, >> >> Can someone take a quick look at IBATIS-522? The patch is simple and we >> had to apply it to our software after upgrading to 2.3.2 so I'd like to know >> if it will eventually be incorporated. >> >> https://issues.apache.org/jira/browse/IBATIS-522 >> >> Tom >> > > >
