-
Notifications
You must be signed in to change notification settings - Fork 129
Integrate changes from microbit-foundation 1.0.0 tag #84
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
Conversation
The aim of this is to create a new 'legacy' branch that has the features of the latest editor but the MicroPython version of the past. This is what we will expect people migrating from microbit.co.uk to use first.
This reverts commit 13ded9b.
VERSION
Outdated
@@ -0,0 +1 @@ | |||
1.0.0 |
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.
From the previous PR:
If we need to update this on this release, can we also add it to the RELEASE_TODO.rst file?
VERSION
Outdated
@@ -0,0 +1 @@ | |||
1.0.0 |
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.
From the previous PR:
Btw, I am not sure why this file is here and what it does, do you have more context @microbit-sam ?
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 think it's only used by the build/deploy scripts so maybe it should be removed from this PR
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.
This still means that on python-editor there are two different places we need change the version number, any way it could be merged into a single source of truth? (After syncing repos)
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.
As VERSION only exists in the foundation repo I think this is something we should solve out of the tag integration process
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.
Yep absolutely. Could you create a new ticket in the python-editor repo to not forget about this?
Comment from previous PR:
|
Comment from previous PR:
|
Comment from previous PR:
|
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 for the update Sam, I've moved the comments from the previous PR to this one.
|
The MicroPython hex in the editor.html file ends without a new line:
Old version of DAPLink will fail to find the end of file record without it (and possible the space at the end of the record line could be a problem as well, I think DAPLink just looks for `:00000001FF\n). |
CHANGELOG
Outdated
1.0.0 | ||
----- | ||
|
||
* Updated MicroPython firmware |
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.
Based on the PR diff, it looks like the MicroPython firmware is the same between bbcmicrobit/PythonEditor@master and [email protected].
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.
Hmm.. I'd based that from the commit message in c4ef9c2
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.
Is the hex file from commit c4ef9c2 the same as in https://github.com/bbcmicrobit/PythonEditor/blob/master/firmware.hex ?
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.
Yes, firmware I've got in my clean branch is from master not the commit
I think I must have checked out the wrong file
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've updated the firmware to correct version and tested
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.
Okay, so I am looking at the v1.0.0 release: https://github.com/microbit-foundation/python-editor/tree/1.0.0
And the hex file doesn't look like it is the same than this PR:
https://github.com/microbit-foundation/python-editor/blob/1.0.0/firmware.hex
https://github.com/bbcmicrobit/PythonEditor/blob/23d73277853c621ada1343cd4fca1e5ff0d026e9/firmware.hex
Is it possible there is a missing commit to cherry pick on top of c4ef9c2?
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've managed to mess it up in the final commit that should have just updated the CHANGELOG and README, will amend and push!
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.
Right, so then the v1.0.0 hex file is the same as bbcmicrobit/PythonEditor@master, correct?
https://github.com/microbit-foundation/python-editor/blob/1.0.0/firmware.hex
https://github.com/bbcmicrobit/PythonEditor/blob/master/firmware.hex
If that's the case we'll also have to remove this first line in the changelog about updating MicroPython.
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.
Yeah I think this is right now, I've updated the CHANGELOG
view-source:https://python-editor-1-0-0.microbit.org/
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.
Great, thank you Sam!
23d7327
to
a5b4549
Compare
a5b4549
to
03438dd
Compare
The PR is ready so I'll merge it, thank you Sam! We can now start working on a PR for v1.1.0 :) |
Replacing #82
Bring in changes from the Microbit Educational Foundation fork