# Github readme.md files aren't managed well

**URL:** <https://forums.suse.com/t/github-readme-md-files-arent-managed-well/15132>\
**Category:** SUSE Rancher Prime\
**Created:** [August 23, 2019, 3:51pm UTC](https://forums.suse.com/t/github-readme-md-files-arent-managed-well/15132 "2019-08-23T15:51:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cprivite](https://avatars.discourse-cdn.com/v4/letter/c/f14d63/32.png) [@cprivite](https://forums.suse.com/u/cprivite)\
**Post date:** [August 23, 2019, 3:51pm UTC](https://forums.suse.com/t/github-readme-md-files-arent-managed-well/15132/1 "2019-08-23T15:51:47Z")

</div>

Once again the main [github.com/rancher/rancher](http://github.com/rancher/rancher) Readme.md isn’t actually showing the current release information for Rancher. It still has 2.2.7 in it even though 2.2.8 is out now and listed as stable.

Even weird is if you set the tag to 2.2.8 and look at the Readme.md it’s talking about rancher 2.1.7.

Can you do something about your process to more correctly update the readme.md files in the released versions to match what’s on the release page?

Alternately, removing the information about release status from the Readme.md works too. That way people won’t get wrong info because they checked a file that hasn’t been updated. You could just put a link in there to say “check the Releases page for the latest info” and never have to update the Readme again. 🙂