> To do this kind of testing in-house before they release to us, would dramatically >slow the > pace of development and increase the "feedback" loop between users and developers. >I > much prefer the occasional annoyance of having to back up to a previous EAP to the >long > development cycle of a more traditional development model.
I agree with the slowdown. But IntelliJ (oh, I meant JetBrains) would get a better feedback, if they would release the eap builds more often like in the good old days one year ago. Tom On Wed, 24 Jul 2002 17:10:07 -0400, "Michael Kirby" <[EMAIL PROTECTED]> wrote: > > > On 24 Jul 2002 at 13:21, Muthu Ramadoss wrote: > > > thats exactly what happened.. worse you cant get rid of that window.. > > its in somekind of a hellish loop. > > > > i wonder what kind of QA is done on eap versions... > > We are the QA...Suck it up.. :-) > > Seriously though. I imagine they have an extensive set of automated tests, as well >as using > the release themselves, but since there are so many ways to use this software, and > environments play such a large role, without wide-spread testing there is no reason >to > guarantee that these early versions will be usable for a specific set of tasks that >any one user > might have. > > To do this kind of testing in-house before they release to us, would dramatically >slow the > pace of development and increase the "feedback" loop between users and developers. >I > much prefer the occasional annoyance of having to back up to a previous EAP to the >long > development cycle of a more traditional development model. > > Mike > --- > [EMAIL PROTECTED] > To obtain my PGP public key, mail "SEND PUB KEY" in the > subject to "[EMAIL PROTECTED]" > _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
