Repository navigation
Add CHANGELOG.md for the Comunity Release milestone (issue 13) - #18
Merged
Merged
Conversation
Documents the "Comunity Release" milestone (QuasarApp#1): CI workflow (QuasarApp#7), README rewrite (QuasarApp#8), LGPLv3 license change (QuasarApp#9), GitHub Pages documentation site (QuasarApp#12) and this changelog (QuasarApp#13). Fixes QuasarApp#13
Closed
EndrII
approved these changes
Oct 13, 2026
Member
Author
|
Status: approved and mergeable, CI green - ready for maintainer merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
CHANGELOG.mddocumenting the "Comunity Release" milestone #1 (issue #13):README.mdrewrite for the fork (Update readme #8), license -> LGPLv3 withCopyright (C) 2026 QuasarApp Group DOO(Change Liense to LGPLv3 #9).UNLICENSE(Change Liense to LGPLv3 #9).With this PR and #8, #9, #12 merged, all issues of milestone #1 are resolved — the milestone itself still needs a maintainer to close it (the QuasarAppCI account has no milestone permission).
Fixes #13