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
Master Behind Release Tag #14306
Comments
ping @mattab |
shouldn't you check out 3.x-dev? |
I'm not developing. I'm pulling to a production machine. |
Yes the same, I mean you would need to pull 3.x-dev and not master? |
@tsteur I'm not exactly sure how you manage PRs here, but |
@Findus23 totally forgot we're still doing this. I suppose we need to stop possibly with Matomo 4. Think we discussed a year ago or so. Since it's not recommended / less secure etc. If someone wants to still use git, they can check out specific release versions. |
I don't think that's the right advice, but you can certainly deprecate I'm sure I used a git repo to merge in a fix/PR I had submitted but had not yet been released. I'd argue that it's important to have that option even if you don't maintain a production branch in the upstream repo. |
FWIW our release scripts will refuse to run if we haven't checked out Obviously, you should run your business as you see fit, but that pattern is designed to ensure that |
I try to keep master up to date with releases but sometimes forget. So it's not safe to rely on |
I have an instance of Matomo that I update using
git
. I pulled master today only to be notified (in the UI) that I don't have the latest version (3.8.0 vs 3.9.1). I came here and confirmed that master is behind the current release tag.Is this intentional? If so, why?
The text was updated successfully, but these errors were encountered: