| Re: [wtp-incubator-dev] Status of M9 build and release and release review |
David M Williams wrote:
That's fine with me. I've frozen any need changes I would be making for the first 1.0M1 release. Doug and Jesper we probably should start looking at what we want to have done for M1.You may note I've moved to "S-builds" instead of I-build for our XSL M9 (writing this note, I see I forgot to change the '8' to a '9' so have fixed that for latest S-builds).I don't recall seeing a confirmation, but neither objections, so I'll assume what I wrote earlier, and we will publish our official M9 on Wednesday 13th, after that, we'll produce an R build, and officially publish it one week after that, Wed., the 20th.The week buffer is always a good idea, just to give adopters time to test the final candidate, to make sure we've not made any last minute mistakes.
David, should I be creating a plan for XSL Tools that follows the new standardized project plan format? I know in some cases this might be changing due to bug 243303.
Okay, let me know as soon as possible because I may have to re-arrange a dentist appoint if the meeting does go on as planned for Wednesday. The sooner I know the better. The outstanding CQ actually has been sitting there for several months, so I figure it slipped through the crack a while ago, they are usually pretty good about getting approval on those small items.Unrelated, you may have noticed some small chance we can't do the review on Wednesday, since the IP Log technically hasn't been officially approved yet, and we do technically have one CQ outstanding that still needs official approval. All of this (if your curious) is just that the people involved have been on vacation ... well, that I we didn't check ahead of time if they'd be available :) I'm 99% sure they can get all the work done by Wednesday, but you never know, so that's why it was scheduled with a chance it might have to be delayed. Just wanted to let all you committers know.
Works for me, and it'll be nice to have the JUnits available easily on the summary build page.Lastly, I may be producing several "extra" S-builds, just because I'm testing/fixing putting JUnit test times on the summary page ... and the incubator builds so quickly it's easy to test a time or two to put on finishing touches.
Dave