Community
Participate
Working Groups
As indicated in cross-project list, there is now a new "maintenance release" of b3 aggregator. http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg06340.html As far as I know (from a quick scan of "fixed bugs") there is no behavior changes so I plan to update the aggregator used for Indigo maintenance builds, as well as for the soon to be Juno builds. And, just documenting that fact here. Please speak up if any concerns.
There is a major improvement that force the model to be migrated : Validation Sets see ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=338738 and associated bugs ) Projets clients needs to upgrade the b3 editor model too, and any bash process needs to be updated/verified if they use/modify the main model.
So, to be clear, you mean even if a project did not use validation sets, then they (everyone) still has make some changes? If that's the case, then I'd prefer to leave "maintenance" alone, and use the new version only for Juno ... unless someone says they absolutely need the new version for maintenance. (I confess, I've still not really understood the impact or "syntax" of validation sets).
I've done this (updated aggregator) for Juno aggregation builds. Don't plan to for Indigo maintenance aggregation builds ... unless someone says we need it. Thanks,
(In reply to comment #3) > I've done this (updated aggregator) for Juno aggregation builds. > > Don't plan to for Indigo maintenance aggregation builds ... unless someone says > we need it. > > Thanks, Sorry for not replying sooner. I totally agree with your choice, indigo should not use b3 new version for avoiding problems. for juno, b3 new version is good.
