Replies: 6 comments 8 replies
-
Is it only possible to release from
Basically I agree with this. |
Beta Was this translation helpful? Give feedback.
-
I think we can release from any branch, not sure about it though. The problem is that the subsplit repo is updated from master automatically. At least this is what I understand. |
Beta Was this translation helpful? Give feedback.
-
Why we don't create 2.0.49.x branch and let subsplit script to handle it as any other branch? If 2.0.49 will be LTS, then we need this anyway, because there will be more releases like this with some important patches. It looks like it already worked for other branches in the past and 2.2.x line too: https://github.com/yiisoft/yii2-framework/branches |
Beta Was this translation helpful? Give feedback.
-
Also, I'm pretty sure this is not a first time when patch release is created not from master, but using old tag as a base. So there must be a way to do this without messing with |
Beta Was this translation helpful? Give feedback.
-
So just tag it from subsplit repo branch? I think this would work, just need a confirmation from @samdark |
Beta Was this translation helpful? Give feedback.
-
Hi guys, sorry for not responding, I've been on vacation. 2.0.49.3 was just tagged. |
Beta Was this translation helpful? Give feedback.
-
I've discussed some options to release 2.0.49.3 with only one thing being reverted without the stuff already merged (marked with 2.0.50 milestone) with @samdark and it's tricky because we have this subsplit repo to be updated from master. I don't have experience with that kind of flow so I need some help regarding handling it properly (it would be so easy without this subsplit).
I proposed something like:
Samdark said it's too risky unfortunately.
Beta Was this translation helpful? Give feedback.
All reactions