Wrong branch for tag 2.3.1 about monolog-bundle HOT 7 CLOSED

ping @fabpot

from monolog-bundle.

👍

from monolog-bundle.

my fault here. What would be the best strategy to "fix" the situation? Retag 2.3.1 correctly bu removing the current tag and force update on Packagist? ping @Seldaek

from monolog-bundle.

@fabpot retagging is an option but not so nice. We could just tag a 2.3.2 properly from the 2.3 branch, but ultimately what I would like is a plan for the next releases. Should bundles really be synced to symfony? If yes then should you or me do the tag? The current situation is a mess, I never know when you'll tag, or from which branch, etc. It requires a lot of synchronization which is not so great.

from monolog-bundle.

I don't think we should force syncing with symfony releases.
For instance, we never released a 2.2 version of AsseticBundle as 2.1 was working with both Symfony versions, thus reducing the maintenance (and then, it has been released as 2.3 which seems pretty weird to me). A similar issue happens for FrameworkExtraBundle: 2.1, 2.2 and master could all work with all symfony versions as of 2.1, except that the composer requirements are forbidding to use the latest features in a 2.2 project.

As we have separate repositories, it would make sense to release these bundles when they have new features, and reducing the number of maintained branches to the minimum needed (which should be 1 now as far as Symfony is concerned as Symfony should not be allowed to break BC anymore requiring to change the bundle)

from monolog-bundle.

I agree that the current situation si not clear. I agree that syncing releases is not required. So, from now on, I will let you guys deals with tagging.

from monolog-bundle.

OK I just deleted the 2.3.1 tag, no need to retag since nothing changed since 2.3.0, it wasn't installable anyway before so I don't think that'll create any problem.

from monolog-bundle.