search

vermiculus / magithub

**DEPRECATED - please use Forge instead!** -- Magit-based interfaces to GitHub
GNU General Public License v3.0
579 stars 63 forks source link

Formalize/stabilize release process #240

Open vermiculus opened 6 years ago

vermiculus commented 6 years ago

Right now, my approach to releases is pretty...ill-defined. I tend to tag a release when I feel the code has both made significant strides since the last release and the code is relatively stable.

Anybody who purports their releases are bug-free is either dishonest to their clients or to themselves, so bug-free is not the goal. However, a few dumb mistakes keep getting made:

I'd propose a makefile target is created that will prepare the worktree for a given release. This phony target could either take the role of a linter -- reporting errors to be fixed manually -- or maybe something more.

Related to #219.

vermiculus commented 6 years ago

Also need to make sure to update version numbers in README badges.