and that would be the same as any previous branch... 1.x still active in Artemis, we cherry-pick fixes all the time... and same with previous branches on activemq.. it's a common thing here.. nothing different.
you rework the console, you bump the release.. and if users still need the older version we can cherry-pick fixes for current production systems. I would say we leave the discussion for when it happens.. it would depend on the extent of the rework.. if it's compatible or not.. etc.. etc... On Thu, Jul 6, 2017 at 1:36 PM, Clebert Suconic <[email protected]> wrote: >> Well, yes and no. Once "released", you kind of have to build off of >> what’s there and continue to support that way of doing things. If what’s >> there doesn’t make any sense and needs to be completely re-organized or >> something, that could be difficult if we have to continue supporting the >> current layout. Kind of like a backwards compatibility thing. I’d like >> a few folks to make sure that what’s there makes some sense going forward >> and adding the stuff that is missing can be done by extending what’s there >> in a way that makes sense. That said, for the first release, if we kind >> of release note the console as a “technology preview, subject to change” or >> similar, I’d be less concerned. > > We would just need to define criteria to bump releases.. > > supposing current master is at 2.2.x... and there's already a console > in place... > > a major rework on the console would bump the release to 2.3.0 or 3.0.0 ? -- Clebert Suconic
