Yep, probably you should look into SVN, which is the official tracking system of the WordPress ecosystem. However, i often do "freeze" a production website and clone it onto a staging server where i test every new update (even core). Only after that, i move onto production and not before having waited at lease a couple of weeks (unless it's some sort of important security update).
I don't think SVN and GIT by themselves do issue tracking, though they may support tagging of issue numbers, they don't offer any ways to publicise ways to work with said repo. I think SourceForge is used for many SVN repos, and GitHub for many git repos.
No no, i mean you have always to contact the devs via the wordpress.org (if it's free) repo. On SVN you might find hints of the current bug tracking, but that's not a standard.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yep, probably you should look into SVN, which is the official tracking system of the WordPress ecosystem. However, i often do "freeze" a production website and clone it onto a staging server where i test every new update (even core). Only after that, i move onto production and not before having waited at lease a couple of weeks (unless it's some sort of important security update).
I don't think SVN and GIT by themselves do issue tracking, though they may support tagging of issue numbers, they don't offer any ways to publicise ways to work with said repo. I think SourceForge is used for many SVN repos, and GitHub for many git repos.
No no, i mean you have always to contact the devs via the wordpress.org (if it's free) repo. On SVN you might find hints of the current bug tracking, but that's not a standard.