9f49dbbc2e
The release:has-stable-branch is useless and should be retired: - The git repository is the true source of information whether a given repo has stable branches or not. The tag is therefore redundant, and often inaccurate (since it's not necessarily updated when a project creates stable branches). - Having "stable" branches does not mean that the repository applies the common stable branch maintenance policy. This tag therefore does not convey any useful information for our downstream users. Whether a project follows stable policy or not is now described using the stable:follows-policy tag. Change-Id: I7d7d24db0de4728977218f9b7fadc060f69c2e55 |
||
---|---|---|
.. | ||
base.py | ||
check_projects_yaml_alphabetized.sh | ||
teamstats.py | ||
universe_dot.py | ||
validate_tags.py |