too quiet

It has been so quiet lately on the newsgroups it's scary. I hope this
means that behind the scenes the IntelliJ folks are making good progress
on introducing support for fundamental new Aurora features.

Jon

13 comments
Comment actions Permalink

Well as far as I heard, the jetbrain guys are busy testing a few new things
with the IDE internally. That is why u can see that bugs that are reported
in the tracker are not being fixed rapidly.
But before they jump into Aurora, I would really prefer all the remaining
bugs to be fixed first. There are just too many bugs that are opened but not
assigned to Arora, and many of those bugs are related to my unsatisfaction.
3.0 was a very major upgrade from 2.6, and the amount of bugs in 3.0 are
growing rapidly everyday. If they don't control the bugs now, when will
they? I know lot of people might have a different opinions. Once Aurora
starts, there will be starting to add features one after another, and so
obviously new bugs will be born. And I am very sure Aurora will be a very
major upgrade from 3.0 with really HOT features that lot of people are
looking for. But I would appreciate that they fix the current bugs with IDEA
3.0 and make it fully stable, before they start on Aurora. Infact I think
alot of people who are NOT members of IDEA's EAP, are looking forward for
bug fixes too.

This is just my suggestion.


Saumendra
Developing in Pleasure............


0
Comment actions Permalink

seems like it's been quiet for a while. if you do a search for the fixed in bugs/features there are quite a few fixed in release 689 and a whole lot in 700. They have also updated a lot of issues making commitments for the Aurora release. All of that being said I think you are correct when you say they are gearing up for the next release.

0
Comment actions Permalink

i agree with you. It seems that they are working on fixing bugs. build 689 has all bug fixes. I'm not sure how they run their release cycles, but it seems like they are working on bug fixes (releases < 700) and aurora features (release 700).

0
Comment actions Permalink

>But before they jump into Aurora, I would really
>prefer all the remaining bugs to be fixed first. There
>are just too many bugs that are opened but not assigned
>to Arora

I agree wholeheartedly.

They set such a high standard with 2.6 - I don't remember 2.6 ever crashing on me, and it was very slick.

I have very few issues with 3.0. My only complaints are that I do see crashes from time to time with the "internal error, you will need to restart IDEA" popup, and as has been oft posted before "Find In Path" sometimes just stops working.

I want a rock-solid coding/refactoring engine - and this means, like you, I'd rather see bug fixes before adding more bells and whistles. They're doing this anyway with the 3.0.x builds, but not all bug fixes are going in to that branch - see "fixed in 700".

We'll obviously get a better idea when we see the scope of the new features planned for 4.0.

0
Comment actions Permalink

I have very few issues with 3.0. My only complaints are that I do see

crashes from time to time with the "internal error, you will need to restart
IDEA" popup, and as has been oft posted before "Find In Path" sometimes just
stops working.

Actually, ALL of such bugs (i.e. internal errors and other critical issues)
are fixed for 3.0.x builds as soon as we find way to reproduce them.

--
Valentin Kipiatkov
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"


"Mark Lee" <jiveadmin@jetbrains.com> wrote in message
news:5568379.1039720856366.JavaMail.jrun@is.intellij.net...

>But before they jump into Aurora, I would really
>prefer all the remaining bugs to be fixed first. There
>are just too many bugs that are opened but not assigned
>to Arora

>

I agree wholeheartedly.

>

They set such a high standard with 2.6 - I don't remember 2.6 ever

crashing on me, and it was very slick.
>

I have very few issues with 3.0. My only complaints are that I do see

crashes from time to time with the "internal error, you will need to restart
IDEA" popup, and as has been oft posted before "Find In Path" sometimes just
stops working.
>

I want a rock-solid coding/refactoring engine - and this means, like you,

I'd rather see bug fixes before adding more bells and whistles. They're
doing this anyway with the 3.0.x builds, but not all bug fixes are going in
to that branch - see "fixed in 700".
>

We'll obviously get a better idea when we see the scope of the new

features planned for 4.0.


0
Comment actions Permalink

689?
"charles decroes" <intellij@decroes.com> wrote in message
news:6004634.1039720545420.JavaMail.jrun@is.intellij.net...

i agree with you. It seems that they are working on fixing bugs. build

689 has all bug fixes. I'm not sure how they run their release cycles, but
it seems like they are working on bug fixes (releases < 700) and aurora
features (release 700).


0
Comment actions Permalink

look at http://www.intellij.net/tracker/idea/browse?_pageSize=4&_searchDefs=1&_sortList1=3&_ascending=false&_secondSortEnabled=false&doSort=true

you can see all the bugs fixed in 700, and if you go a couple of pages down you start to see what they have fixed for the 689 build which hasn't been released yet.

0
Comment actions Permalink

On Thu, 12 Dec 2002 18:21:26 +0000, charles decroes wrote:

in bugs/features there are quite a few fixed in release 689 and a whole
lot in 700. They have also updated a lot of issues making commitments for
the Aurora release. All of that being said I think you are correct when


Does it matter that there fixed in 689/700 when 688 is the only one
currently available?

0
Comment actions Permalink

Yes, it makes a huge difference. We know that they are actively working on correcting the bugs and that they will be available shortly. In the past they have been very good about doing short release cycles (at least eap cycles). Being able to see the bugs beinf fixed lets us know they are making progess.

0
Comment actions Permalink

What ever great features they add, all I hope is that Aurora should be built
in such a way that it shouldn't consume anymore memory then 3.0. I have no
more ram slots on my computer (4 slots are full with Rambus ram), and if
aurora consumes a large amount of memory like Oracle JDeveloper(memory
sucker), then I have to say forget it.
By the way, I wonder how many people are happy with Oracle JDeveloper.

Saumendra
Developing in Pleasure.......


0
Comment actions Permalink

Mark Lee wrote:

I have very few issues with 3.0. My only complaints are that I do see
crashes from time to time with the "internal error, you will need to
restart IDEA" popup, and as has been oft posted before "Find In Path"
sometimes just stops working.


I also have some problems when switching from another KDE screen back to
IDEA. The windows just stays empty and doesn't redraw. Unfortunately I
didn't fid a way how to reproduce it or at least to find a pattern when
this happens (it does not all the time).

Best regards,

Dirk Dittert

0
Comment actions Permalink

I've seen this behaviour (very rarely) too.

I ALT-TAB'ed to Mozilla, and when ALT-TAB'ing back to IDEA the whole IDEA frame window was just grey. I left it for about five minutes but it never came back. There was no disk thrashing or apparent CPU hogging.

What I remember doing in IDEA was a few find-in-paths and move class refactorings immediately after starting IDEA.

I couldn't find a way to repeat it either, so didn't post a bug/issue.

This was 687 on KDE 3.0.5.

0
Comment actions Permalink

I had the same occasional problem with KDE 3.0.3 and multiple desktop.
have you opened a TRACKER issue ?
we need one and nect time it happens, we must capture a thread dump.

Edo

Dirk Dittert wrote:

Mark Lee wrote:


>>I have very few issues with 3.0. My only complaints are that I do see
>>crashes from time to time with the "internal error, you will need to
>>restart IDEA" popup, and as has been oft posted before "Find In Path"
>>sometimes just stops working.


I also have some problems when switching from another KDE screen back to
IDEA. The windows just stays empty and doesn't redraw. Unfortunately I
didn't fid a way how to reproduce it or at least to find a pattern when
this happens (it does not all the time).

Best regards,

Dirk Dittert



--
Edoardo Comar
Cape Clear Software
http://www.capeclear.com

Download the New! Beta Release
http://www.capeclear.com/beta

Register for our Technical Webinars - Every Thursday via WebEx
See http://www.capeclear.com/news/webinars/ for details

0

Please sign in to leave a comment.