Someone mentioned automated testing of upgrade paths. This is exactly
what needs to happen. Hopefully the Tempest folks can work with the CI
team in the G timeframe to incorporate upgrade path testing for the
I am strongly in favor of this. :)
That was already identified as a priority 6 months ago, but the stars
weren't aligned very well and it apparently fell off. Sounds like a good
Design Summit discussion topic (in QA ?) to revive this and make sure
that work is done in Grizzly.
FWIW I hope to be able to open the Session submission website tomorrow.