Results 469 comments of Malcolm Smith

After discussion, we agreed the following: * Constantly changing the default GitHub branch would make it too easy to merge PRs to the wrong branch and affect an already-released version...

One more thought: if Briefcase detects a [development version number](https://github.com/pypa/setuptools_scm/#default-versioning-scheme) like 0.3.9.devX or 0.3.9+dYYYYMMDD, it should still attempt to use a `0.3.9` template branch before falling back on `main`. Otherwise,...

FYI, here's a list of Chaquopy's current binary Python packages, sorted by number of downloads in the last 6 months: zcat chaquo-access.log.{2..182}.gz | grep -E 'GET /pypi-7.0/.*\.whl HTTP.*pip/' | cut...

> Running the test suite with the _actual_ packaged Python and environment would be an interesting long term goal, but there's a bunch of complications. Firstly, the "deployed" environment won't...

> It could also potentially remove the need for explicit calls to `update`. By checking for modification dates on the sources folders, or the hash of `requires` definitions, or changes...

Other open issues that may involve updating the Android template: * https://github.com/beeware/briefcase/issues/547 * https://github.com/beeware/rubicon-java/discussions/75#discussioncomment-3224352

The above comment is valid for the current Rubicon template. After we switch to Chaquopy, the `abiFilters` setting will be compulsory, because the Chaquopy plugin requires it. I did this...

> "Toga... user interface code isn't often unit tested..." _yet_ :-) This is something I'm hoping to address (in the grand scheme of things). Definitely, but I was referring to...

A couple of recent breakages which would have been caught by a simple build test: * [briefcase-template#32](https://github.com/beeware/briefcase-template/pull/32): AppImage configuration was mislabeled in pyproject.toml. * [#816](https://github.com/beeware/briefcase/pull/816): Flatpak CPython installation was broken...

Actually, I see there are build tests in the CI now, but these problems weren't caught for other reasons: * briefcase-template [#31](https://github.com/beeware/briefcase-template/pull/31) and [#32](https://github.com/beeware/briefcase-template/pull/32): Template updates should trigger a Briefcase...