As discussed, we are changing some of the platform advocates for (a)
geographical, and (b) platform familiarity reasons. This will be
reflected in the automatic assignment of reviewers on PRs.
We are pretty much all affected in this shuffle!
@keymanapp-test-bot skip
(cherry picked from commit 9bff83fa00)
- Create and sign source package
- Upload to mentors.debian.net
- Create (and optionally push) commit with updated changelog file
based on stable branch
- Create (and optionally push) commit with updated changelog file
based on master branch
This change also slightly modifies `echo_heading` and outputs a
mark. This will show to the left of the line as well as in the
scroll bar in a terminal in VSCode [[1]] and will help to find the
headings if you have a lot of output in between.
[1]:https://code.visualstudio.com/updates/v1_69#_setmark-sequence-support
(cherry picked from commits ae61410cc9,
2a55ffb024, 9232c20569,
420cc0814d, 9f7b85834a,
and ae0378a57f)
1. Renamed form UfrmNGrokOptions to UfrmServerOptions
2. Renamed kmdev-server to just plain server
3. Tidied up npm versioning to use VERSION_WITH_TAG
This last point should help avoid confusion as now only CI release
builds will ever generate a package.json with a.b.c, a.b.c-alpha or
a.b.c-beta. Local and test builds will always have the corresponding
-test or -local environment appended. This also helps avoid issues if
we accidentally publish an incorrect version.
* Move old notes into an old/ folder to clarify their pending removal
and add a note to the top of each file.
* Cleanup macos.sh script to fix various issues.
As the build environment documentation is duplicated across each of the
Keyman platform projects, it has become somewhat convoluted and
inconsistent. This PR moves all the mac-based and shared documentation
into docs/build, with placeholders for Windows and Linux documentation
to be moved in the next PR.
The idea is that a developer can configure their box to build any of the
available projects for that platform (web and android build on all three
main dev platforms).
Keeping the build documentation in one place makes it much simpler to
keep it consistent and up-to-date as well, as well as keeping us aware
of potential dependency conflicts between projects.
The icing on the cake is the resources/devbox/macos/macos.sh script,
which I have tested and takes a bare metal mac box through to a full
Keyman development environment (except XCode, there's always something!)
This is a cherry-pick of PR#4223:
- Add script to create debian source package
- Update debian metadata based on Debian repos
- Remove some lintian warnings and errors
- Remove support Xenial
- Reduce size of icon
- Omit confusing values from gbp.conf
