Simple maintenance improvements (#1918)
* Use license file from gnu.org Downloaded from: https://www.gnu.org/licenses/gpl-3.0.txt * Add missing final newline * Fix link * Fix shellcheck warnings * Move donation header one level up * Fix typos * Stop mixing tabs and spaces * Trim trailing whitespace
This commit is contained in:
@@ -42,7 +42,7 @@ For small fixes or incremental improvements simply fork the repo and follow the
|
||||
|
||||
After reporting you should aim to answer questions or clarifications as this helps pinpoint the cause of the issue.
|
||||
|
||||
### Donations
|
||||
## Donations
|
||||
|
||||
I improve Flameshot in my free time because I want to create something good for everyone to use.
|
||||
If you want you can donate some bucks [here](https://www.paypal.me/lupoDharkael).
|
||||
|
||||
18
docs/RFC.md
18
docs/RFC.md
@@ -40,7 +40,7 @@ following.
|
||||
|
||||
+ Any changes breaking compatibility to command line flags or config files.
|
||||
+ Any major changes to the UI
|
||||
+ Substantial new features like new tools.
|
||||
+ Substantial new features like new tools.
|
||||
|
||||
Some changes do not require an RFC:
|
||||
|
||||
@@ -48,12 +48,12 @@ Some changes do not require an RFC:
|
||||
|
||||
not change meaning".
|
||||
|
||||
+ Improving translations.
|
||||
+ Improving translations.
|
||||
+ Additions that strictly improve objective, numerical quality criteria
|
||||
|
||||
(warning removal, speedup, better platform coverage, etc.)
|
||||
|
||||
+ Additions only likely to be _noticed by_ other developers-of-flameshot,
|
||||
+ Additions only likely to be _noticed by_ other developers-of-flameshot,
|
||||
|
||||
invisible to users-of-flameshot.
|
||||
|
||||
@@ -76,7 +76,7 @@ beforehand, to ascertain that the RFC may be desirable; having a consistent
|
||||
impact on the project requires concerted effort toward consensus-building.
|
||||
|
||||
The most common preparations for writing and submitting an RFC include talking
|
||||
the idea over on our [official Slack server](flameshotworkspace.slack.com) or opening an issue on github for discussion.
|
||||
the idea over on our [official Slack server](flameshotworkspace.slack.com) or opening an issue on github for discussion.
|
||||
|
||||
## What the process is
|
||||
|
||||
@@ -86,7 +86,7 @@ In short, to get a major feature added to Flameshot, one must first get the RFC
|
||||
merged into the RFC repository as a markdown file. At that point the RFC is
|
||||
"active" and may be implemented with the goal of eventual inclusion into Flameshot.
|
||||
|
||||
+ Fork the Flameshot repo
|
||||
+ Fork the Flameshot repo
|
||||
+ Copy `docs/0000-template.md` to `docs/RFC/0000-my-feature.md` (where "my-feature" is
|
||||
|
||||
descriptive). Don't assign an RFC number yet; This is going to be the PR
|
||||
@@ -170,9 +170,9 @@ next major release.
|
||||
In general, once accepted, RFCs should not be substantially changed. Only very
|
||||
minor changes should be submitted as amendments. More substantial changes
|
||||
should be new RFCs, with a note added to the original RFC. Exactly what counts
|
||||
as a "very minor change" is up to the development team.
|
||||
as a "very minor change" is up to the development team.
|
||||
|
||||
|
||||
|
||||
|
||||
## Reviewing RFCs
|
||||
|
||||
@@ -216,11 +216,11 @@ Some RFC pull requests are tagged with the "postponed" label when they are
|
||||
closed (as part of the rejection process). An RFC closed with "postponed" is
|
||||
marked as such because we want neither to think about evaluating the proposal
|
||||
nor about implementing the described feature until some time in the future, and
|
||||
we believe that we can afford to wait until then to do so.
|
||||
we believe that we can afford to wait until then to do so.
|
||||
|
||||
Usually an RFC pull request marked as "postponed" has already passed an
|
||||
informal first round of evaluation, namely the round of "do we think we would
|
||||
ever possibly consider making this change, as outlined in the RFC pull request,
|
||||
ever possibly consider making this change, as outlined in the RFC pull request,
|
||||
or some semi-obvious variation of it." (When the answer to the latter question
|
||||
is "no", then the appropriate response is to close the RFC, not postpone it.)
|
||||
|
||||
|
||||
@@ -60,4 +60,4 @@ A button has been added to open the sidebar. This tool was previously only acces
|
||||
* Enable Pin and Text tool by default. (#443)
|
||||
* Fix the problem that moving or resizing does not affect screenshot. (#459)
|
||||
* Fix problem with re-enabling disabled tray icon (#495)
|
||||
* Fix compilation problem against Qt 5.15.
|
||||
* Fix compilation problem against Qt 5.15.
|
||||
|
||||
@@ -1,40 +1,40 @@
|
||||
# 0.9 Release Notes
|
||||
Thanks to all the testers and contributors that helped make version 0.9! We are very excited to have improved many
|
||||
bugs and added new features in version 0.9.
|
||||
bugs and added new features in version 0.9.
|
||||
|
||||
|
||||
## Known Issues
|
||||
- Fractional scaling issues are not resolved. We are working with Qt upstream on this issue.
|
||||
- Fractional scaling issues are not resolved. We are working with Qt upstream on this issue.
|
||||
|
||||
|
||||
## New Features
|
||||
- Improved MacOS support. MacOS is now officially supported and we will resolve any reported issues on this platform.
|
||||
|
||||
- Thanks to SignPath we are able to offer digitally signed windows releases.
|
||||
|
||||
- Thanks to SignPath we are able to offer digitally signed windows releases.
|
||||
- Improved Wayland support
|
||||
- Behind the scenes we configure flameshot to automatically run on xcb. This significantly improves the
|
||||
- Behind the scenes we configure flameshot to automatically run on xcb. This significantly improves the
|
||||
wayland experience. This resolves issues with multimonitor setups and copying to the clipboard
|
||||
|
||||
- New option to allow the the clipboard image to be a jpeg instead of a png. This may reduce bandwidth when pasting the
|
||||
|
||||
- New option to allow the clipboard image to be a jpeg instead of a png. This may reduce bandwidth when pasting the
|
||||
image into chat or email clients
|
||||
|
||||
- New global shortcut menu. All actions hotkeys are fully customizable.
|
||||
|
||||
- Ability to take "symmetric" selections by holding down the Shift key while resizing the selection.
|
||||
- New global shortcut menu. All actions hotkeys are fully customizable.
|
||||
|
||||
- Ability to take "symmetric" selections by holding down the Shift key while resizing the selection.
|
||||
|
||||
- The rectangle tool will now round the corners of the rectangles based on the current thickness
|
||||
|
||||
- All imgur uploads are now tracked in the "Upload History" menu. This makes it much easier to delete of images off imgur
|
||||
or find the upload link later.
|
||||
|
||||
- Added "check for new release" feature. This allows users on MacOS / Windows / and AppImages to easily check for updated versions.
|
||||
- Added "check for new release" feature. This allows users on MacOS / Windows / and AppImages to easily check for updated versions.
|
||||
|
||||
- New option for setting a "fixed save path". When this is enabled a user will no longer need to set the path for images
|
||||
that are saved.
|
||||
that are saved.
|
||||
|
||||
|
||||
|
||||
## Fixes
|
||||
- Under certain circumstance the circle count could get set to the wrong number with large numbers of undo / redo. This
|
||||
has been fixed.
|
||||
|
||||
has been fixed.
|
||||
|
||||
- Close after capture has been removed. This feature was not well implemented and lead to numerous bugs.
|
||||
|
||||
@@ -10,11 +10,10 @@ These are the code changes that need to take place
|
||||
These are the steps for actually making the release
|
||||
- [ ] Download all binaries from CI run started from PR related to code changes shown above
|
||||
- [ ] Create sha256 for each binary and compare against sha256 shown in the CI to verify there was no corruption or inserted malware.
|
||||
- [ ] Create a new "New Release" in githhub and explain changes in release notes
|
||||
- [ ] Create a new "New Release" in github and explain changes in release notes
|
||||
- [ ] Upload all binaries and sha's
|
||||
- [ ] Update flatpak manifest for flathub: https://github.com/flathub/org.flameshot.Flameshot
|
||||
- [ ] Update flatpak manifest for flathub: https://github.com/flathub/org.flameshot.Flameshot
|
||||
- [ ] Push snapcraft edge release to stable
|
||||
- [ ] If this is a major release coordinate with sign path on signed windows binaries
|
||||
- [ ] If this is a major release coordinate with sign path on signed windows binaries
|
||||
- [ ] Update change log on [website](https://github.com/flameshot-org/flameshot-org.github.io/) data/changelog.md
|
||||
- [ ] Update version on [website](https://github.com/flameshot-org/flameshot-org.github.io/blob/master/_coverpage.md)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user