Skip to content

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

Merged
merged 15 commits into from
Feb 1, 2019

Conversation

microbit-sam
Copy link
Collaborator

Replacing #82


Bring in changes from the Microbit Educational Foundation fork

VERSION Outdated
@@ -0,0 +1 @@
1.0.0
Copy link
Collaborator

@microbit-carlos microbit-carlos Jan 31, 2019

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
Copy link
Collaborator

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 ?

Copy link
Collaborator Author

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

Copy link
Collaborator

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)

Copy link
Collaborator Author

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

Copy link
Collaborator

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?

@microbit-carlos
Copy link
Collaborator

Comment from previous PR:

Can't comment on the editor.html file in the code view, so I'll add the comment here.

Looks like the version string is different on this branch, if your starting point was bbcmicrobit/PythonEditor master, then it means something has changed it from '0.1.0' to '0.0.0':

PythonEditor/editor.html

Lines 72 to 73 in 5a0e321

<!-- VERSION INFORMATION -->
VERSION = "0.0.0";

Both bbcmicrobit/PythonEditor@master and foundation/[email protected] have that string as '0.1.0'. I think we should divert from both and set this to '1.0.0', as that is what we are calling this version of the editor.

@microbit-carlos
Copy link
Collaborator

Comment from previous PR:

Can we also update the changelog to include info about all these changes?

@microbit-carlos
Copy link
Collaborator

Comment from previous PR:

The MicroPython version in the editor.html and firmware.hex files are different, could we replace these to be the same as the [email protected]?
That way the future tag in this repo will be representative of the deployed version 1.0.0 and any other cherry picked commits should apply cleanly.

Copy link
Collaborator

@microbit-carlos microbit-carlos left a 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.

@microbit-sam
Copy link
Collaborator Author

  • Removed VERSION
  • Updated editor.html VERSION
  • firmware.hex and editor.html firmware are the same (tested both)
  • Updated CHANGELOG
  • Updated README from ./show to ./bin/show (this is wrong in the foundation README)

@microbit-carlos
Copy link
Collaborator

The MicroPython hex in the editor.html file ends without a new line:

:00000001FF </div>

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
Copy link
Collaborator

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].

Copy link
Collaborator Author

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

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

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

Copy link
Collaborator Author

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

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator Author

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!

Copy link
Collaborator

@microbit-carlos microbit-carlos Jan 31, 2019

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.

Copy link
Collaborator Author

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/

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thank you Sam!

@microbit-sam microbit-sam force-pushed the 1.0.0-clean branch 2 times, most recently from 23d7327 to a5b4549 Compare January 31, 2019 17:43
@microbit-carlos
Copy link
Collaborator

The PR is ready so I'll merge it, thank you Sam!

We can now start working on a PR for v1.1.0 :)

@microbit-carlos microbit-carlos merged commit 7617562 into bbcmicrobit:master Feb 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants