-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong branch for tag 2.3.1 #45
Comments
ping @fabpot |
👍 |
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 |
@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. |
I don't think we should force syncing with symfony releases. 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) |
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. |
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. |
@Seldaek The 2.3.1 tag have been made on the master branch instead of the 2.3 branch.
Now when installing symfony 2.3.1 monolog-bundle require monolog-brige >=2.4-dev
The text was updated successfully, but these errors were encountered: