Hi all, We've been working towards a second release of the Reporting suite. The original plan was simply to quickly release an updated version that depends on kepler-2.2 instead of kepler-2.1, so reporting users could benefit from the 2.2 improvements. But we've since made changes/improvements to the kepler suite modules that reporting-at-head depends on, so we now plan to release a kepler 2.3 that this new version of Reporting can use. This means a less ambitious kepler 2.3 than previously discussed; we can simply change our old definition of kepler 2.3 to be 2.4. I have yet to update the outdated roadmap page, or create a 2.4 target and retarget bugs, but I can do that soon.
I haven't seen anything go into the kepler suite modules post 2.2 that shouldn't be included, so I'd like to cut this kepler 2.3 release from near head, when we are ready. I also plan to cut reporting near head when the time comes; I haven't seen anything that should be excluded. Christopher - the last kepler developer change that I've seen go into ptII was aschultz r61021. Kepler 2.2 uses ptII r60245. Aaron made a number of commits post 60245 that are work on memory leaks, and seem like they'd be good to include. If no one objects to this plan, and if we determine we don't need to make any commits to ptII (seems unlikely, and we should be able to determine this and let you know soon), would you be able and willing to cut and clean a branch of ptII post r61021 in the near future for kepler 2.3 to use? Let me know if anyone has objections or comments on this plan. Thanks, Derik _______________________________________________ Kepler-dev mailing list [email protected] http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
