[issue2551365] Document use of a VCS to manage a deployed tracker with upgrades.

New submission from John Rouillard:

Issue 2550764 suggested making the login/logout items in page.html conditional
by a setting in config.ini.

Editing the template is the recommended method of doing this and the requestor
does that. However it is not the best when upgrading to a newer version of the
tracker.

There is no documentation (probably should be part of the admin guide) on how
to use a version control system with a vendor branch to make merging new tracker
template releases into an existing tracker easier.

Somebody should write one. While I hate to say it, git would probably be the VCS
that gets used as an example. I think mercurial or fossil would be easier, have fewer
footguns etc. But git is the mainstream tool for this now.

----------
components: Documentation
keywords: Effort-Low, GSOC, StarterTicket
messages: 8144
nosy: rouilj
severity: normal
status: new
title: Document use of a VCS to manage a deployed tracker with upgrades.
type: rfe

_________________________________________________
Roundup tracker <[email protected]>
<https://issues.roundup-tracker.org/issue2551365>
_________________________________________________