release.txt

//
// Copyright (c) 2020 NVI, Inc.
//
// This file is part of the FSL10 Linux distribution.
// (see http://github.com/nvi-inc/fsl10).
//
// This program is free software: you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation, either version 3 of the License, or
// (at your option) any later version.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program. If not, see <http://www.gnu.org/licenses/>.
//

To make a release:

. git checkout master
. Update version and dates in *.adoc
. git push
. git tag <tag>     (<tag>=v2, or whatever)
. git push --tags
. Follow making_gh-pages.txt to publish; through the first push is already done

Versioning

. Incremental changes accumulate on master
. For wording changes in documents, increment patch level in documents
  affected, e.g., 1.0.1, and republish gh-pages
. For changes in function, e.g., a new feature in fsadapt, increment minor
  level in affected documents (if any), e.g., 1.1, and republish
. A new release would be made if the changes should be retrofitted by existing
  users, all docs updated with the new version numbers and republished
. A major change would increment the major level, e.g., 2.0.0, and would be a
  new release with new updated documents and their version numbers, but it
  isn't clear what the use case would be, the next OS would go to a new repo,
  e.g., fsl11.