... | ... | @@ -24,6 +24,8 @@ So- it is only when you have a concrete design in place ready for evaluation tha |
|
|
|
|
|
# Configuring your GitLab for a beta
|
|
|
|
|
|
_(Applicable only if you use GitLab.)_
|
|
|
|
|
|
The steps below will configure your GitLab repository for a beta. Your files will NOT be exposed to anyone who is not a member of your project (either explicitly added by you, or within your group).
|
|
|
|
|
|
1. Go to your repository settings, then "General".
|
... | ... | @@ -34,18 +36,25 @@ The steps below will configure your GitLab repository for a beta. Your files wil |
|
|
6. Disable Analytics, Wiki, Snippets, and Operations. (Unless you wish to use these features)
|
|
|
7. Click "Save Changes".
|
|
|
|
|
|
# Preparing for a beta
|
|
|
|
|
|
_These instructions presume you are using GitLab for version control._
|
|
|
After you configured your repository, follow the steps below for tracking changes to your files:
|
|
|
|
|
|
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.
|
|
|
|
|
|
# Tidy your package, and submit a beta request
|
|
|
|
|
|
Starting a beta is easy from a developer's end. You just need to make sure two things, and a moderator will take care of creating your room for you.
|
|
|
|
|
|
Your ticket will be closed and you will be notified when it is fulfilled.
|
|
|
|
|
|
1. Your beta package aligns to the requirements as outlined in \["Release Package Requirements"\](<https://gitlab.deterrencedispensed.com/deterrence-dispensed/information-and-tutorials/-/wikis/For-Developers/Resources/Release-Package-Requirements>), but for a beta.
|
|
|
2. You submit a Beta Request at the \[Help Desk\](<https://gitlab.deterrencedispensed.com/deterrence-dispensed/help-desk/-/issues>)
|
|
|
|
|
|
# Configuring the beta channel
|
|
|
|
|
|
> **Note:** This step can only be done by a RocketChat administrator.
|
|
|
> **Note:** This step can only be done by a RocketChat administrator after your beta request is approved.
|
|
|
|
|
|
1. Create a channel with the following format: `#beta.username_projectslug`
|
|
|
2. Populate the description and topic.
|
... | ... | |