|
|
|
This is a guide and process guidance on how to conduct a beta.
|
|
|
|
|
|
|
|
# Preparing for a beta
|
|
|
|
_These instructions presume you are using GitLab for version control._
|
|
|
|
|
|
|
|
1. Commit your files. You must have the following files in your package as highlighted in the [Release Package Requirements](https://gitlab.deterrencedispensed.com/deterrence-dispensed/information-and-tutorials/-/wikis/For-Developers/Resources/Release-Package-Requirements) guidance document.
|
|
|
|
2. Create a "Release" with a "tag" in the following format off of your primary/develop branch: `vX.x` where `X` is major version, and `x` is minor version. (i.e, if this is your products first beta, you could use `v0.1`.)
|
|
|
|
3. Do not use the release artifacts archive automatically bundled by GitLab- create a zip file with all your files EXCEPT the Natives, STEP, and all Git-related folders.
|
|
|
|
4. Upload your file to the beta channel.
|
|
|
|
|
|
|
|
# Configuring the beta channel
|
|
|
|
> **Note:** This step can only be done by a RocketChat administrator.
|
|
|
|
|
| ... | ... | @@ -21,5 +31,6 @@ The Rules: |
|
|
|
5. Set the designer as the Channel Owner.
|
|
|
|
6. Announce the beta
|
|
|
|
|
|
|
|
## Pro-tips:
|
|
|
|
- An announcement can be updated to display a persistent message in the channel. |
|
|
\ No newline at end of file |
|
|
|
# Pro-tips:
|
|
|
|
- An announcement can be updated to display a persistent message in the channel, and can be found in its channel settings.
|
|
|
|
- It's strongly, **STRONGLY** recommended that you do not include source files (STEPs, Natives) in your beta. |
|
|
\ No newline at end of file |
