- This topic has 36 replies, 11 voices, and was last updated 20 years, 9 months ago by
.
-
Posts
-
All,
M7 introduced a few bugs and incompatiblities that we have to work around. It’s taking some development effort to fix and retest.
I don’t know about anyone else but I think it’s getting to the point where I would be more willing to wait for 3.7 if it would mean we could get support for M8 in it as soon as M8 is released. Based on past Eclipse release patterns it would seem that M8 will be out around the end of the month. I think I’d rather wait a few more weeks for 3.7 + M8 rather than get 3.7 + M7 now and not get M8 support.
So, unless ME is committed to have support for M7 now and M8 soon after it’s release I would rather wait for M8 to get 3.7? Looking at ME release patterns it looks like if we get a 3.7+M7 in a couple of days then based on ME trends we probably won’t get an M8 release of ME. Can you comment on this thought process at all Scott? What do other people think? Would anyone else rather wait for 3.7 + M8 soon after M8 is out or would people rather get 3.7+M7 now and have to wait for M9 (or whatever they’ll call it) for the next ME release?
Mike
A few new features and polishing would be nice. 🙂 But that may complicate the situation more than Scott and ME would like. So let’s assume no new features except what features M8 might be giving us already. What would Scott’s and everyone’s thoughts be on that situation?
Mike
Mike & All,
We’re working very hard to get everything working and tested on M7, but since it is both a large upgrade in MyEclipse functionality (3.7 GA has over 90 fixes/enhancements over 3.7RC2), it’s proving to be a bear. We’ll get it out though. Re M8, we should be able to support it much faster than M7 since MyEclipse will only include a few fixes over 3.7 GA (hopefully :-). We know the 3.0 builds are important, but we also want to be sure everything is all buttoned up before we ship it to thousands of users. The pain is just too great for support if it isn’t. 😉
I can wait too. 🙂 However, I would like my waiting to be as effective of waiting as possible. Meaning what I don’t want to have happen is to have waited this long after and finally get a 3.7 + M7 release only to have M8 come out 1 week later. So, I guess what’s I’m saying is I’d rather wait 1 or 2 extra weeks for an M8 compatible release rather than get an M7 compatible release soon and then possibly not get a timely M8 release.
Now If I understand your comments correctly Scott, you’re saying that we’ll get an M7 release soon and an M8 release relatively soon after M8 comes out? That would be fine with me if that’s the plan. But if the plan is to get M7 support and then skip M8 support or get an M8 release a month or so after M8 has been out then I’d rather skip the M7 release in favor of an M8 compatible release soon after M8’s release. I understand how much work it must be to create 3.0 builds so I’d like the 3.0 compatible releases that we do get to be as bleeding edge as possible rather than obsolete a week after release.
Mike
[quote]
Now If I understand your comments correctly Scott, you’re saying that we’ll get an M7 release soon and an M8 release relatively soon after M8 comes out?
[/quote
That’s the plan.Guys,
The ME team *really* appreciates you being so patient with the releases. We realize that its only so many times you can hear “… lots of breakage in this M build” before you go nuts and storm our offices. I just wanted to drop a line letting you know that internally, the ME team absolutely without a doubt places customers and their needs as our #1 driving force. We add the features you ask for, get rid of the bugs that make you crazy and internally beat the hell out of ME before it ships to make sure we aren’t going to screw up the productivity of our users if a really annoying bug sneaks in.With that said, 3.x support is definately on our plate because you guys want it, and that’s not a problem; but then we implicitly tack on the ‘beat the hell out of it internally’ part to make sure that we aren’t releasing really stable 2.x builds, and half-assed 3.x builds that generally piss people off.
When Eclipse 3.0 goes final, I think for M8 and after things will smooth out quite a bit because we won’t be chasing API changes or breakages. Although the rule of thumb is ‘expect the worst’, but chances are things will speed up soon.
Thanks for the info. Riyad, I hope it didn’t sound like I was complaining or being impatient or anything. I think you guys do a great job and I definitely don’t take for granted the fact that the ME team does 3.0 releases nor the amount of work that must go into them. I was just trying to get an idea as to what the plan was for support of M8 once it came out and was trying to take some heat off of the ME team by throwing out the idea to skip an M7 release in favor of an M8 release because I would prefer to have an M8 release rather than an M7 release if I had to make a choice. However, thanks to Scott’s info I know that a choice is not needed so I’m cool.
Thanks,
MikeM8 release have many changes and I think that ME need M7 release
ME for M8 can’t be quick, but M8 is feature freeze and ME can add your features after M8, only
favorite features in M8 (I like this in ME too, for xml and jsp editor) is code folding in java editorregards
Haris PecoWell, since I know many are interested I thought I’d give an update on 3.7GA for M7. We worked all weekend on QA, but found a packaging problem late on Sunday. Basically, when the PDE exports plugins, it creates temporary directories into which to compile the plugin’s java code. We ran into a problem where some of the product jars were simply missing a class or two when the export didn’t report any errors at all. Nothing. All good, just missing classes. After much frustrating digging we found that if Eclipse generates a path name that is longer than what is supported by the platform (215 chars on Windows, 256 on Linux) that the export would silently fail and simply ignore the class while reporting the build was successful. Naturally, something as wacky as this took awhile to run down, but we finally did. Anyway, the 3.7 GA build needs one more cursory round of QA, just to ensure that the packaging problem was addressed. If that’s all OK, we’ll release it late tonight (CST, your ‘late tonight’ may vary).
Sorry for the delay and thanks to all for your continued patience and understanding that if it isn’t ‘right’, we’re not shipping it.
@scott wrote:
Anyway, the 3.7 GA build needs one more cursory round of QA, just to ensure that the packaging problem was addressed. If that’s all OK, we’ll release it late tonight (CST, your ‘late tonight’ may vary).
great news !
is there a list of changes compared to RC2 (or should I just wait for the download..) ?
ivar,
For now the changelog for 3.7 GA will be almost identical to 2.7 GA (if not identical), you can oogle it here:
http://www.myeclipseide.com/ContentExpress-display-ceid-33.html
