3 ms·
I'm always surprised how phenomenally hard it is to get people to test alphas and release candidates - it isn't until the actual major release hits the floor th
by jeresig 17y ago
I'm always surprised how phenomenally hard it is to get people to test alphas and release candidates - it isn't until the actual major release hits the floor that a ton of input starts to roll in. Every release I think it'll be different but I have yet to be proven right.
That being said, 1.4.1 is effectively "it" for a while (at least a month or so). It's shipping in Visual Studio and Drupal 7 so it doesn't matter what bug fixes come in after this, a lot of people will be using this version of jQuery.
- jeresig 17y agoI should clarify: We do get a ton of feedback during the alpha/release candidate phases - it's just that there always seems to be a few things that end up slipping through in the end, one way or the other, hence the soon-after .1 release.
- pierrefar 17y agoBut the key thing here is that the project responds very quickly to the new feedback and releases an updated version. How many projects do that? Not many. Serious kudos for creating such a responsive culture in the project.
- johns 17y agoSorry John, I didn't intend that to come off as negative. I know it's challenging to get people to test. I'm a big jQuery proponent and I don't even test until after the release (sorry). I'm happy to see the release and to know this is the Visual Studio version.
- jeresig 17y agoNo worries - I definitely appreciate feedback. Glad you're enjoying jQuery :)
- jeff18 17y agoWhy would a significant portion of jQuery users want to be unpaid QA testers? It surely is a noble cause and is great for the community at large, but it's naive to expect that more than a tiny minority will actually contribute when they can just sit back and reap the rewards. ;)