On 12/18/20 5:34 AM, Eduard Heimbuch
Hey SCM-Manager community,
we just released the last minor version of SCM-Manager for
this year. We added some useful new features and fixed bugs
you reported to us. As always check our blogpost for more
It's been quite a year for the SCM-Manager. We officially
released SCM-Manager 2 and have been working relentlessly to
improve SCM-Manager and the many plugins we published yet. We
won't stop with this and already have big plans for the next
year regarding SCM-Manager.
We love your feedback and greatly appreciate every single
user and supporter of SCM-Manager.
We wish you a merry Christmas and a healthy new year.
Your SCM-Manager Team
BTW: If you didn't know yet, we also post SCM-Manager
news on Twitter. Checkout our hashtag #scmmanager2
Thanks for the update and thanks to the entire SCM-Manager team for
such outstanding work over the years. I rely on the product for my
personal repos. If I were still doing corporate, I'd have it for my
dev teams, as well :). I can't help but notice that y'all have been
blazing through updates since the move to version 2... this has
resulted in many new features that I appreciate. The rss feed has
been awesome for helping me keep up. However, I was wondering if
y'all had any plans to incorporate an auto-update feature (user
select-able)? Y'alls track record of not breaking stuff (or
providing quick and effective solutions when things do go wrong) is
very good and I, personally, would feel comfortable with such a
feature. If not auto-update, then maybe a, "An update is available,
would you like to install it?", feature.
I'm on FreeBSD and every time y'all announce an update, I go through
the same motions:
create a snapshot of the filesystem in ZFS
stop scmserver (an rc script)
download the unix tarball and unpack it in scm-manager/packages
copy it to /usr/local/scm-manager-whatever-version and symlink it to
fixup the script to use /bin/sh (prolly not needed, but comforting)
do some linking of var stuff and whatnot
start the new service
tail the log
do a test commit
if everything is swell delete the snapshot and have coffee
These days, the entire process takes about 2-3 minutes (I follow a
note/script) and is pretty safe (thanks to ZFS). It's not a big
deal, but the update feature would at least keep human error at a
If doing the installation is an issue, then just a notice in
scm-manager (even an icon and hover text) that an update is
available would be helpful.
Merry Christmas and Happy New Year to y'all, as well.