@diosmosis @tsteur @mattab Switching to the rebranded packages (with new namespaces) might maybe cause problems while updating, as some plugins might still use the old namespace until they are updated.
Any ideas how we should solve that issue? Should we update the plugins before, so they use the actual available namespace? Or shall we still include both packages in Matomo 4 (old and rebranded ones), so both namespaces are still available - and remove the old one in Matomo 4.1 or so?

and remove the old one in Matomo 4.1 or so?

I reckon this won't be possible since some people will update from older 3.x or 2.X to 4.1.

Updating plugins first can cause issues too if anything fails there.

Ideally the components would have both the new Matomo and the old Piwik classes but that might not be easily doable. Although the components typically maybe don't have too many classes so could be done maybe. Otherwise I suppose it should be fine maybe as long as the plugins don't access any component during update? They might though... also people manually updating core etc will have problems.

Do we even need to update the components from Piwik to Matomo or wait until we do this also for core?

Ideally the components would have both the new Matomo and the old Piwik classes but that might not be easily doable. Although the components typically maybe don't have too many classes so could be done maybe.

Could this be done via inheritance? Ie:

namespace Piwik;

class Abc extends Matomo\Abc {
  // empty
}

Could this be done via inheritance? Ie:

I guess that should work. Should we add those classes to the packages or to Matomo itself?

Not sure what's easier?

I suppose we would need to make sure the autoloader still finds the files etc.

Very crazy thought... can the auto loader do that? Recognise Piwik namespace, then look for the matomo file that includes Matomo class, then do dynamically a if (!class_exists($piwikNamespaceClass, $doNotLoadFile)) { class $piwikNamespaceClass extends $matomoNamespaceClass }

Not sure if we can extend classes that way dynamically...

@tsteur I'll give it a try and implement it that way if possible

@tsteur found an even simpler solution using class_alias:

That's pretty cool 👍

Should be ready for review. Remaining package is piwik/device-detector. But I will do some more refactorings there before releasing a new rebranded version.