feat: api
, feat: integration / plugin
, feat: webrtc
, subj: ui/ux
, subj: security
stat: in progress
while the PR is not ready for merge (and remember to remove the label when it is). When naming your Pull Request, please start the name with one of the following tags for identifying changes:[NEW] WhiteBoard integration
)[FIX] OTR timeout problems (#629, #2535)
)[BREAK] Change notification setting type from boolean to string
)release-candidate
branch is ready to become a real release, some actions need to be carried out. First, the release branch is merged into master
(since every commit on master
is a new release by definition). Next, that commit on master
must be tagged for easy future reference to this historical version. Finally, the changes made on the release-candidate
branch need to be merged back into develop
, so that future releases also contain these bug fixes.release-candidate
based on develop
:release-candidate
branch, especially regarding issues they have worked on. Any bug-fixes applied to release-candidate
should immediately be cherry-picked into develop
.master
branch:master
and also into release-candidate
(and develop
if the bugfix cannot wait for the release branch to be finished).latest
). If you don't know the version you're working on, access /api/info
on your instance. Include as much detailed information as you can, such as animated gifs and/or screenshots of errors, code samples, and reproduction steps.feat: accessibility
, feat: embed
, feat: livechat
, etc.)subj: mobile
, subj: security
, subj: ui/ux
, etc.)type: bug
, type: new feature
, type: discussion
, etc.)contrib:
, so the community can make a contribution. We categorize them into easy
, intermediate
and experts needed
to help contributors pick an issue to work on when joining the project, based on how difficult the work we believe the issue demands.