- This topic has 13 replies, 6 voices, and was last updated 20 years, 1 month ago by
.
-
Posts
-
Will all jsp editor bugs be *really* fixed in that release without any slowdown, validation errors, indexing lock-ups etc?
1) Indexing lockups have been fixed with the new quickfix posted in the forums here http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-4223-highlight-myeclipsequickfix20041004+zip.html, which also aparently fixed some XML validation issues
2) Validation errors, which ones? Do you have a specific example?
3) “any slowdown”, please be more detailed.
The more specific you are, the more accurately I can determine if a bug is already filed and +1 it, or file a new bug and target it for 3.8.3. We have a lot of bugs targetted for that release (and features) and want to knock them all out, but since we don’t live in a unicorn-laden fantasty world, I’d imagine that some might get pushed to 3.9 due to time contraints. However you guys help us prioritize what the most annoying bugs are so we can get those chopped out ASAP.
I don’t have any specific bug reports other than the ones I already posted. I just meant that the JSP has been in a bad shape for quite some time now. We’ve seen the 3.8.1 release, 3 quickfixes, then the 3.8.2 release that was supposedly to fix all major bugs, then there was the quickfix again and now we are with in the current situation where people are seemingly still not ultimately happy with the jsp editor.
I just hope that with 3.8.3 basic editting will just work again, for everyone, and that no quickfixes are needed anymore only days after its release. I fully understand that it might not be feasible to squash each and every bug, but a return to the pre-3.8 level of stability for basic jsp editting would be the least.
Sorry I can’t be more specific right now. I just installed the 3.8.2 quickfix. As soon as I have any more detailed findings I shall of course post them 🙂
henk,
I get the jist of what you are saying and we will do multiple betas of 3.8.3 so if you wouldn’t mind (when that time comes) it might be helpful if you could try and grab 1 or 2 of them to see if the annoyances you are having are getting fixed… if you are interested you can join the QA team we have that does beta testing.So if 3.8.3 is coming out in December-ish, I assume we will see 3.9 RC1 sometime in 2005? The current roadmap says Q4…please tell me that’s not Q4 2005…
Sorry to bug you guys about release dates, but the features listed for 3.9 are the ones I’ve been waiting for since day 1: Visual JSP, Visual Struts, Visual HTML, hopefully all(?) on Linux.
I can’t comment on the 3.9 timeline as I don’t have the details, but its DEFINATELY not Q4 2005, it was originally for Q4 2004, but we had a lot of polish and work that needed to go in before we did another round of just feature additions (3.9).
@support-rkalla wrote:
henk,
I get the jist of what you are saying and we will do multiple betas of 3.8.3 so if you wouldn’t mind (when that time comes) it might be helpful if you could try and grab 1 or 2 of them to see if the annoyances you are having are getting fixed… if you are interested you can join the QA team we have that does beta testing.Hi Riyad,
actually what is the requirements for members of the QA board? 🙂
E.g. do they have to regularly allocate time for testing the functionality, do they have to test all functionality, or just reporting bugs which they bump into during normal usage?
Regards,
Robert Varga
Rob, I actually sent a notice when we first formed it to invite you, if you are not part of it we would appreciate it if you would join.
The method of beta testing is really to install the betas, use them in your every day work, and report problems to us in a special forum. Does that sound like something you want to help work on?
I sent an answer to Jim about it a couple of weeks ago, that unfortunately I would not be able to regularly allocate time for testing, but would report bugs when I come around them during my regular work.
Unfortunately currently I am working on a part, where there is not too much ME functionality, which I encounter (except for debugging, which mostly seems to work, aside from always receiving not being able to replace code in the server messages). I am not really surprised by that error message actually, considering the weird project setup we have where there are even classes generated with the same name instead of classes we have in our source, which clearly no debugger should be able to follow.
As I wrote to him as well, if that is not enough, I must decline the offer, otherwise I would gladly report bugs the same way as I have done so far….
I haven’t received an answer from him, yet… probably he is also overwhelmed with his work, like me. 🙁
I really hate too quickly approaching deadlines 🙂
Regards,
Robert
Robert,
It was not my intent to ignore your email. We are always appreciative when offered assistance in any form.
I’ve added your account to the quality board, and you should now have access to QA testing forum.
We appreciate your continued support.
@subscriptions wrote:
Robert,
It was not my intent to ignore your email. We are always appreciative when offered assistance in any form.
I’ve added your account to the quality board, and you should now have access to QA testing forum.
We appreciate your continued support.
Hi Jim,
I did not assume that you ignored it, either…. if you remember, I also replied with a couple of weeks delay, because of being overwhelmed with work to be done…
Thanks,
Robert
