✔ Create release builds/ branches
(Completed by Pierre henri Seylan on June 1, 2016)
Comments
Pierre henri Seylan on February 3, 2016:
Context:
As the release is approaching, we should set up a branch that will be used to shape the release version of the app.
NOTE: the development branch must stay as it is, without the tabs hiddenÂ
Details:
1. Create release branch: Create a branch called "client-release" and "client-release-beta" see below for details about those branches
2. set up builds if possible set up the jenkins for this branch as well
2.1 public release build: (for all users) contains the following tabs:
Load project tab
Browse tab
Notifications
installer package: only the client app
2.2 Beta release build: (only for beta users)
all tabs except chat tab (see below)
Installer package: client + sampler
3. Hide the chat tab from the app
Hide the chat tab from the app
make the workspace messages notifications to open the project's url when clicked, instead of opening the chat in app (keep the linking to chat for later)
make the project commit notifications to link to load project tab (with rev folder open, like for pull requests)
Comments
Pierre henri Seylan on February 3, 2016:
Context:
As the release is approaching, we should set up a branch that will be used to shape the release version of the app.
NOTE: the development branch must stay as it is, without the tabs hiddenÂ
Details:
1. Create release branch:
Create a branch called "client-release"
and
"client-release-beta"
see below for details about those branches
2. set up builds
if possible set up the jenkins for this branch as well
2.1 public release build: (for all users)
contains the following tabs:
- Load project tab
- Browse tab
- Notifications
installer package: only the client app2.2 Beta release build: (only for beta users)
- all tabs except chat tab (see below)
Installer package: client + sampler3. Hide the chat tab from the app