Remove trailing white spaces
This commit is contained in:
parent
88e3edc7d2
commit
f971c149d6
|
@ -2,7 +2,7 @@ I confirm (by marking "x" in the [ ] below):
|
|||
|
||||
- [ ] This is not a troubleshooting question. [Troubleshooting questions go here: http://www.mattermost.org/troubleshoot/](http://www.mattermost.org/troubleshoot/).
|
||||
- [ ] This doesn't reproduce on web browsers (such as in Chrome). If it does, [issue reports go to the Mattermost Server repository](https://github.com/mattermost/platform/issues).
|
||||
- [ ] I have read [contributing guidelines](https://github.com/mattermost/desktop/blob/master/CONTRIBUTING.md).
|
||||
- [ ] I have read [contributing guidelines](https://github.com/mattermost/desktop/blob/master/CONTRIBUTING.md).
|
||||
|
||||
---
|
||||
|
||||
|
@ -14,10 +14,10 @@ Issue in one concise sentence.
|
|||
**Steps to reproduce**
|
||||
|
||||
<!--
|
||||
Please include:
|
||||
Please include:
|
||||
- Operating System
|
||||
- Mattermost Desktop App version (See **Help > Version Number**)
|
||||
- Mattermost Server version (See **Mattermost Menu > About Mattermost**, where **Mattermost Menu** can be accessed by clicking on three dots next to your profile picture)
|
||||
- Mattermost Desktop App version (See **Help > Version Number**)
|
||||
- Mattermost Server version (See **Mattermost Menu > About Mattermost**, where **Mattermost Menu** can be accessed by clicking on three dots next to your profile picture)
|
||||
- Clear steps to reproduce the issue
|
||||
-->
|
||||
|
||||
|
|
10
NOTICE.txt
10
NOTICE.txt
|
@ -43,7 +43,7 @@ SOFTWARE.
|
|||
|
||||
## bootstrap
|
||||
|
||||
This product contains a modified portion of 'bootstrap', which is an HTML, CSS, and JavaScript framework for developing responsive, mobile first
|
||||
This product contains a modified portion of 'bootstrap', which is an HTML, CSS, and JavaScript framework for developing responsive, mobile first
|
||||
projects on the web, by Twitter, Inc. and Bootstrap Authors.
|
||||
|
||||
* HOMEPAGE:
|
||||
|
@ -111,7 +111,7 @@ THE SOFTWARE.
|
|||
|
||||
## electron-devtools-installer
|
||||
|
||||
This product contains a modified portion of 'electron-devtools-installer', which allows an easy way to ensure Chrome DevTools extensions into Electron,
|
||||
This product contains a modified portion of 'electron-devtools-installer', which allows an easy way to ensure Chrome DevTools extensions into Electron,
|
||||
by Samuel Attard.
|
||||
|
||||
* HOMEPAGE:
|
||||
|
@ -500,7 +500,7 @@ under section (i) of this paragraph due to such counterclaim.
|
|||
|
||||
## react-bootstrap
|
||||
|
||||
This product contains a modified portion of 'react-bootstrap', Bootstrap 3 components for front-end framework built with React, by Stephen J. Collings,
|
||||
This product contains a modified portion of 'react-bootstrap', Bootstrap 3 components for front-end framework built with React, by Stephen J. Collings,
|
||||
Matthew Honnibal, Pieter Vanderwerff and react-bootstrap.
|
||||
|
||||
* HOMEPAGE:
|
||||
|
@ -1363,7 +1363,7 @@ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|
|||
|
||||
## mocha-circleci-reporter
|
||||
|
||||
This product contains 'mocha-circleci-reporter', a mocha reporter that supports Circle CI, via a combined jUnit and Spec reporter
|
||||
This product contains 'mocha-circleci-reporter', a mocha reporter that supports Circle CI, via a combined jUnit and Spec reporter
|
||||
output, by Glenn Morton.
|
||||
|
||||
* HOMEPAGE:
|
||||
|
@ -1558,7 +1558,7 @@ SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
|
|||
|
||||
## webpack-merge
|
||||
|
||||
This product contains 'webpack-merge', which concatenates arrays and merges objects creating a new object, useful in
|
||||
This product contains 'webpack-merge', which concatenates arrays and merges objects creating a new object, useful in
|
||||
configuring webpack, by Juho Vepsäläinen and SurviveJS.
|
||||
|
||||
* HOMEPAGE:
|
||||
|
|
|
@ -4,7 +4,7 @@ This document outlines the release process for the Mattermost Desktop App. It is
|
|||
|
||||
## Release Timeline
|
||||
|
||||
Notes:
|
||||
Notes:
|
||||
- All cut-off dates are based on 15:00 GMT (UTC-00) on the day stated.
|
||||
- T-minus counts are measured in "working days" (weekdays other than major holidays concurrent in US and Canada) prior to release day.
|
||||
|
||||
|
@ -15,7 +15,7 @@ Pre-work for the current release begins at the code complete date of the previou
|
|||
### B. (T-minus 12 working days) Release Date Announcement
|
||||
|
||||
1. PM:
|
||||
- Post this checklist in Desktop App channel
|
||||
- Post this checklist in Desktop App channel
|
||||
- Confirm date of marketing announcement for the release and update Desktop App channel header if needed
|
||||
- Create meta issue for release in GitHub to let contributors and users know about the upcoming release. See [example issue](https://github.com/mattermost/desktop/issues/271).
|
||||
- Prepare JIRA tickets for the next release, with a corresponding vX.X prefix
|
||||
|
@ -23,14 +23,14 @@ Pre-work for the current release begins at the code complete date of the previou
|
|||
- Cut final release with code-signing for Windows and Mac builds
|
||||
- Queue desktop app for a 15-minute team testing
|
||||
2. Dev/PM:
|
||||
- Prioritize reviewing, testing, and merging of pull requests for current release until there are no more tickets in the [pull request queue](https://github.com/mattermost/desktop/pulls) marked for the current release
|
||||
- Prioritize reviewing, testing, and merging of pull requests for current release until there are no more tickets in the [pull request queue](https://github.com/mattermost/desktop/pulls) marked for the current release
|
||||
|
||||
### C. (T-minus 7 working days) Code Complete and Release Candidate Cut
|
||||
|
||||
**Stabilization** period begins when all features for release have been committed. During this period, only **bugs** can be committed to the release branch. Non-bug pull requests are tagged for the next version.
|
||||
|
||||
1. PM:
|
||||
- Post this checklist in Desktop App channel
|
||||
- Post this checklist in Desktop App channel
|
||||
- Verify all items in the last posted release checklist are complete
|
||||
- Mail out mugs to any new contributors
|
||||
- Coordinate testing:
|
||||
|
@ -46,8 +46,8 @@ Pre-work for the current release begins at the code complete date of the previou
|
|||
4. Marketing:
|
||||
- Tweet announcement that RC1 is ready
|
||||
- Queue art work for Twitter announcement
|
||||
|
||||
### D. (T-minus 6 working days) Release Candidate Testing
|
||||
|
||||
### D. (T-minus 6 working days) Release Candidate Testing
|
||||
|
||||
1. PM:
|
||||
- Post this checklist in Desktop App channel
|
||||
|
@ -60,13 +60,13 @@ Pre-work for the current release begins at the code complete date of the previou
|
|||
- Daily triage of hotfix candidates and decide whether and when to cut next RC or final
|
||||
- Post links to final tickets for next RC to the Desktop App channel
|
||||
- Submit PRs for hotfixes against the release branch, and review, test and merge prior to next RC
|
||||
4. Build:
|
||||
4. Build:
|
||||
- Push next RC to acceptance and announce in Destkop App channel with new RC link
|
||||
5. PM:
|
||||
- Test the new RC to verify fixes merged to the release branch work and post in Desktop App channel after testing
|
||||
- Test the new RC to verify fixes merged to the release branch work and post in Desktop App channel after testing
|
||||
- Update the meta issue with download links to the new RCs and a list of approved fixes
|
||||
|
||||
### E. (T-minus 4 working days) Release Candidate Testing Finished
|
||||
### E. (T-minus 4 working days) Release Candidate Testing Finished
|
||||
|
||||
1. PM:
|
||||
- Post this checklist in Desktop App channel
|
||||
|
@ -90,7 +90,7 @@ The final release is cut. If an urgent and important issue needs to be addressed
|
|||
- Post this checklist in Desktop App channel
|
||||
- Verify all items in the last posted release checklist are complete
|
||||
2. Build:
|
||||
- Tag a new release (e.g. 1.1.0) and run an official build which should be essentially identical to the last RC
|
||||
- Tag a new release (e.g. 1.1.0) and run an official build which should be essentially identical to the last RC
|
||||
- Post in Desktop App channel with links to all supported distributions and SHA-256 checksum
|
||||
3. PM:
|
||||
- Update the links in [Mattermost download page](https://www.mattermost.org/download/) and [installation guides](https://docs.mattermost.com/install/desktop.html)
|
||||
|
@ -129,8 +129,8 @@ If a bug fix release is required, run through the following steps:
|
|||
|
||||
### G. (T-minus 0 working days) Release Day
|
||||
|
||||
1. PM:
|
||||
- Post this checklist in Desktop App channel
|
||||
1. PM:
|
||||
- Post this checklist in Desktop App channel
|
||||
- Verify all items in the last posted release checklist are complete
|
||||
- Post key dates for the next release in the header of the Desktop App channel and remove links to RC candidates
|
||||
- Confirm marketing has been posted
|
||||
|
@ -142,9 +142,9 @@ If a bug fix release is required, run through the following steps:
|
|||
### H. (T-plus 10 working days) Release Updates
|
||||
|
||||
1. PM:
|
||||
- Post this checklist in Desktop App channel
|
||||
- Post this checklist in Desktop App channel
|
||||
- Verify all items in the last posted release checklist are complete
|
||||
- Post and review [Mattermost Security Updates](https://about.mattermost.com/security-updates/) for the Desktop App
|
||||
- Update Security Issues spreadsheet with issue number from posted update (e.g. v3.2.0.1)
|
||||
- Confirm the Security Researchers list on the [Responsible Disclosure Policy](https://www.mattermost.org/responsible-disclosure-policy/) is up to date
|
||||
- Review community installers for the Desktop App and update version numbers if there are any discrepencies https://www.mattermost.org/installation/
|
||||
- Review community installers for the Desktop App and update version numbers if there are any discrepencies https://www.mattermost.org/installation/
|
||||
|
|
Loading…
Reference in a new issue