-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates release documentation #2177
Updates release documentation #2177
Conversation
AndreMiras
commented
May 7, 2020
- Links both Travis and GitHub CI build systems
- Updates the PyPI release process (handled by the CI)
Also one point I'd like to discuss. |
doc/source/contribute.rst
Outdated
- [ ] Build and run the [on_device_unit_tests](https://github.com/kivy/python-for-android/tree/master/testapps/on_device_unit_tests) app using buildozer. Check that they all pass. | ||
- [ ] Build and run the following [testapps](https://github.com/kivy/python-for-android/tree/master/testapps) for arch `armeabi-v7a` and `arm64-v8a`: | ||
- `python3 setup_testapp_python3_sqlite_openssl.py apk` | ||
- [ ] `python3 setup_testapp_python3_sqlite_openssl.py apk` | ||
- [ ] `armeabi-v7a` | ||
- [ ] `arm64-v8a` | ||
- [ ] Check that the version number is correct |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would modify these lines, since, IMHO, the on_device_unit_tests
app has the same functionality than testapp_python3_sqlite_openssl
plus a little more (we can check device orientation,if service is working, kivy's keyboard options...). So, I would suggest to test on_device_unit_tests
, because we also could avoid to do the local build (since we have it done in an isolated system with github actions). Still, I would put the command needed to perform a local build for a given arch, just in case that github actions fails or who knows...
Also I would suggest to put the command relative to the project (not inside testapps
) since I think that, if you take an programming IDE like pycharm, the default terminal path is at project level, so it will make easier to copy/paste the command and run it from inside an IDE without entering the testapps
directory. Also I think that is more explicit.
- [ ] Build (or download from github actions) and run the following [testapps](https://github.com/kivy/python-for-android/tree/master/testapps/on_device_unit_tests) for arch `armeabi-v7a` and `arm64-v8a`:
- [ ] on_device_unit_tests
- [ ] `armeabi-v7a` (cmd: `python3 testapps/on_device_unit_tests/setup.py --arch=armeabi-v7a --debug`)
- [ ] `arm64-v8a` (cmd: `python3 testapps/on_device_unit_tests/setup.py --arch=arm64-v8a --debug`)
Anyhow, I would suggest to have @inclement approval for the suggested changes I made (he has far better vision than mine and this is very sensitive stuff...), for your changes, no problem at all,so you have my approval.
Thanks 😄
09380ee
to
3d516b3
Compare
Thanks @opacam I've addressed your comments. |
doc/source/contribute.rst
Outdated
- [ ] `armeabi-v7a` (cmd: `python3 testapps/on_device_unit_tests/setup.py --arch=armeabi-v7a --debug`) | ||
|
||
- [ ] `arm64-v8a` (cmd: `python3 testapps/on_device_unit_tests/setup.py --arch=arm64-v8a --debug`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mmmm..my mistake in here, I realized that I gived to you a wrong command, sorry 😬, this is more appropiated:
- [ ] `armeabi-v7a` (cmd: `python3 testapps/on_device_unit_tests/setup.py --arch=armeabi-v7a --debug`) | |
- [ ] `arm64-v8a` (cmd: `python3 testapps/on_device_unit_tests/setup.py --arch=arm64-v8a --debug`) | |
- [ ] `armeabi-v7a`:: | |
cd testapps/on_device_unit_tests && PYTHONPATH=.:../../ python3 setup.py apk --ndk-dir=<your-ndk-dir> --sdk-dir=<your-sdk-dir> --arch=armeabi-v7a --debug | |
- [ ] `arm64-v8a`:: | |
cd testapps/on_device_unit_tests && PYTHONPATH=.:../../ python3 setup.py apk --ndk-dir=<your-ndk-dir> --sdk-dir=<your-sdk-dir> --arch=arm64-v8a --debug |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually had some doubt as I thought I tried in the past with cd
-ing and we couldn't.
Anyway, now I'm think we should maybe keep this simple and not give the command example at all
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like including the command example because the intention of this doc is to make preparing a release as absolutely thoughtless as possible. Perhaps it would be nice to move it to a makefile command that builds the release targets and prints some clear information about where they were output (but of course don't feel the need to do that here).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ei guys I fixed the command: PYTHONPATH should include p4a sources and testapp sources:
PYTHONPATH=.:../../
That is why didn't work for you @AndreMiras
3d516b3
to
267b368
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. The reason for using markdown-style formatting was indeed so that it can easily be pasted across, but having it look right is good. I guess we could alternatively use markdown formatting but code-format the whole thing, or just make a github template for it (I believe different issue templates are possible via url parameters?)
doc/source/contribute.rst
Outdated
- [ ] `armeabi-v7a` (cmd: `python3 testapps/on_device_unit_tests/setup.py --arch=armeabi-v7a --debug`) | ||
|
||
- [ ] `arm64-v8a` (cmd: `python3 testapps/on_device_unit_tests/setup.py --arch=arm64-v8a --debug`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like including the command example because the intention of this doc is to make preparing a release as absolutely thoughtless as possible. Perhaps it would be nice to move it to a makefile command that builds the release targets and prints some clear information about where they were output (but of course don't feel the need to do that here).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!!
Thanks guys for the feedback. |
@AndreMiras I haven't looked at this much before, but it looks here like the template would just be a dropdown option, which would be quite clear. |
Yeah I will give it a try then. But using triple backquotes when sharing the bug log is not that complex, yet most of bug reports don't have it. Same thing for avoiding duplicated bugs creation 😅 |
- Updates the PyPI release process (handled by the CI) - Links both Travis and GitHub CI build systems - Reformats the release checklist to blockcode for markdown
267b368
to
afa99bb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks again!!
I won't look into the dedicated issue template just now. So let's merge this minor improvement until we try out for a better solution |
🔖 v2020.06.02 * Adds missing requests sub dependencies (kivy#2221) * Bumps to Gradle 6.4.1 (kivy#2222) * Bumps to Cython==0.29.19 (kivy#2220) * Updates install and troubleshooting docs (kivy#2219) * Bumps to Ubuntu 20.04 (kivy#2218) * Attempt to improve the issue template (kivy#2217) * Add `opencv_extras` recipe (kivy#2209) * Split logic for build modes & debug symbols (kivy#2213) * Troubleshoot SSL error (kivy#2205) * Remove superfluous recipes fixes (kivy#2202) * Add tests for hostpython3 recipe (kivy#2196) * Fix for 'cannot find setuptools module' (kivy#2195) * Rename `Hostpython3Recipe` class to camel case (kivy#2194) * Fix `test_should_build` (kivy#2193) * Add initial tests for python3 recipe (kivy#2192) * PythonActivityUtil helper for unpacking data (kivy#2189) * Fixes flake8 errors post update (kivy#2191) * Share PythonUtil.java between bootstraps (kivy#2188) * Java code linting using PMD 6.23.0 (kivy#2187) * Deletes deprecated renpy Python{Activity,Service}.java (kivy#2186) * Removes java concurrency/ folder (kivy#2185) * Reuse common AssetExtract.java (kivy#2182) * Use common Hardware.java (kivy#2183) * Moves kamranzafar/ java directory to common/ (kivy#2184) * Updates release documentation (kivy#2177) * Fixes service only unittest loading (kivy#2181) * Narrows some context manager scopes (kivy#2179) * Downgrades to SDL2 2.0.9 (kivy#2180) * Bump to SDL2 2.0.10 & extract .java from SDL2 tarball (kivy#2113) * Adds pygame recipe (kivy#2164) * Adds macOS install instructions (2165) * Removed python2 support mention from README (kivy#2162) * Adding more assets (kivy#2132) * Get --add-source working for dirs in Gradle builds (kivy#2156) * Fixes python build with macOS venv (kivy#2159)