I *COMPLETELY* disagree. Do you understand what the purpose of an EARLY ACCESS PROGRAM is? If you don't like this kind of approach then I'd suggest downloading the last release and sticking with it until the next full release. The whole point to an EAP is to, over time, generate the large numbers of bugs that are being reported so that they can be catalogued, triaged and worked on.
"Saumendra Poddar" <[EMAIL PROTECTED]> wrote in message an4ube$sua$[EMAIL PROTECTED]">news:an4ube$sua$[EMAIL PROTECTED]... > > To the management group of Intellij, > > Well right now the bug database for the IDEA 3.0 product is now containing > request for just too many Bugs, Features, Duplicate record of bugs, and lots > of Nonescence too. > > I strongly feel that Intellij should just freeze their bug database for the > IDEA product at this situation. > > I am sure that Intellij has already made a decision on what features are > going to be in IDEA 3.0, and what are not. > > So my suggestion is > 1) Just FREEZE the bug database for the time being so that no one can post > any more bugs. > > 2) Go through the entire bug database and clear one bug after the other. > > 3) If there are feature requests in the bug database that needs to be > implemented, then add the feature. If the feature request is beyond the > scope of IDEA 3.0, then just CLOSE that perticular record in the database > with relevant information. Infact there are currently hundreds of us people > testing IDEA now, and many of us have our own views and opinion about a > interesting feature that can be implemented, but it is not possible to full > fill everyone's request, so draw a border line. > > 4) Do severe testing within your organization and see if there are other new > bugs growing from fixing bugs. Don't just throw it on us and say "Here is > build #651, go ahead, download it and test it". > > 5) DON'T RELEASE any builds until the whole bug database has been gone > through and cleared. If this procedure takes a little time, give the time > for it. > > 6) Keep us noted from time to time what bugs are being fixed, and what > features are being currently implemented instead of just releaseing a > build. > > 7) Once everything is cleared from your side, and ALL the bug records have > been closed. Release a build for us to test and then unfreeze the bug > database. > > This way u will have be able to have control of the product and everyone > else will be satisfied that their request in the bug database has been taken > care of with appropiate actions. > > > Please provide your comments on what u think about my suggestion. > > Saumendra > > > _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
