This GIST is here simply to demonstrate some workflows I've found helpful in guaranteeing a well-developed backlog for iteration teams. That said, workflows can be as simple or as complex as you need for your organization/project. At scale though, it's highly desirable to have a backlog as beautifully maintained as your products as their qualities are interdependent. And you'll see this point surface in retrospectives/feedback over time.
First off, DO NOT have workflows that looks like this:
RELATED: Artifacting.md
Versioning is an ancient problem, but this GIST mostly focuses on the computing era and versioning for software. This primer details a few versioning tactics along with some advisories and warnings.
Who is this for? Historically this would have been the bread and butter of the Release Manager, but these majestic creatures are long extinct. These days DevOps is responsible for automating the SDLC, but this material can only serve to enrich anyone interested in or involved in the software industry.
RELATED: Git Branching Strategies, Versioning, Artifacting, SDLC - ALM & CICD
Artifacting is the process of packaging a project prior to release, and is essential as it mitigates many risks in both producing and consuming software products. Beyond simple archives, there are many types of packaging -- often language or framework dependent -- which have been developed to suit various use cases.
This primer demonstrates how to package files as zip and tar.gz; leverage an .artifactignore file similar to .gitignore; and generate and use a checksum file.
[!TIP]
| # Prints a section header. | |
| # | |
| # Features | |
| # - Autosizes to terminal if $width -gt $COLUMNS | |
| # - Specifying width as 4000 works... | |
| # - Adjust first two sanities for stricter usage | |
| # * Currently sets width to half terminal width | |
| # * Currently rounds down odd to even width automatically | |
| # - Customizable outside and inside fill characters | |
| # - Nofill style option |
