No M5a?
What on earth happened? Traditionally, Eclipse M5 represents a low point in the Eclipse development cycle. If you saw Erich Gamma and John Wiegand's great JavaOne talk last year, it is the lowest dip in the rope. Teams scramble to get features in and stability suffers, causing us to blow the milestone. I know 'cause I've blown a few.
This is normal for the Eclipse development cycle. Does this mean that the dreaded "a" is still to come?
Steve
This is normal for the Eclipse development cycle. Does this mean that the dreaded "a" is still to come?
Steve
posted by Steve at
8:40 AM
4 Comments:
This year I tested the I-builds leading up to M5 to ensure that I would not personally be "blamed" for an M5a. We also did an EMF build against the pending M5 bits to make sure that went okay. It does seem that one annoying bug slipped in between Wednesday and Friday, namely 173741 but I can change my preferences to avoid this bug.
By
Anonymous, at 9:22 AM
I personally blame EclipseCon prep for all the shady work that goes into M5 ;)
By
Chris Aniszczyk (zx), at 10:20 AM
Yeah, I wondered whether it would as well. Interestingly, it's a couple of weeks earlier in the frame than the last release dates from the 3.2 and 3.1 releases. Maybe it's to reduce the amount of work done over the post-Christmas sprint?
By
AlBlue, at 11:55 AM
I'm pretty sure that moving the date had a lot to do with it. M5 is (gasp) pretty stable.
By
Steve, at 6:46 PM
Post a Comment
<< Home