Skip to content
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

June 2018 release #1938

Closed
wants to merge 134 commits into from
Closed

Conversation

rachel-fenichel
Copy link
Collaborator

@rachel-fenichel rachel-fenichel commented Jun 26, 2018

Release notes:

Cleanup and testing:

jcyang43 and others added 30 commits April 16, 2018 01:33
… Blockly.FlyoutVertical & Blockly.FlyoutHorizontal
Mark some properties @Protected instead of @Private so they can be used by subclasses
Both are only used by the hue constants, which are already deprecated.
Rewrote Blockly.checkBlockColourConstant_(..).
 * Last argument is now the expected value of the constant (replacing
   the `removed` argument). The prevents warnings when a Msg colour
   constant is overridden (the correct way).
 * If a value for the constant is not found, do not warn (google#1790).
…mations

Move block animation code to a new file and rebuild
…le#1795)

 * Warn if jsonInit() receives a colour attribute without a value.
 * Extract colour init code into function.
 * Adding block type name to prior warnings.
…google#1796)

These namespaces use to contain the original block hue constants,
but were deprecated (via comment, except for procedures) over a year
ago. With the removal of those constants, the declarations were
creating empty, unused objects.
…nt_base

Create base classes for block and variable events
Move events back up to core, because moving it to a separate folder was a mistake.
…essages

Add comment messages and rebuild
The function only returns 1 for the two cases it was used on,
making the scale multiplication a no-op.
rachel-fenichel and others added 24 commits June 7, 2018 10:05
…oogle#1911)

 * Improved Blockly.XML comments.
 * Support JSDOM as an alternate parser under Node.js
 * Throw standard errors instead of goog.asserts.
 * Adding textToDomDocument_ and override in gulpfile.
Adding a link back to the "Running JavaScript" page.
This captures changes to core/xml.js that are required by
Node, since the gulpfile builds from the compressed files.
Replacing all Closure goog. library calls from BlockFactory, with the exception of the ColorPicker and the test for the warning about running without Closure. This includes (almost) all goog.provide and goog.require statements.
Expand %{..} references in toolbox <button> and <label>
Fix case of redeclared var (i) in Blockly.Block.prototype.jsonInit
…code

Revert breaking changes to BlockFactory
Rebuild on develop before cutting a release
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@rachel-fenichel
Copy link
Collaborator Author

I'm closing this PR and replacing it with #1944 so that cherry-picks can go into a branch on Blockly instead of in my repo.

@rachel-fenichel rachel-fenichel deleted the rc/june_2018 branch June 27, 2018 00:07
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.

More package-private property violations.
10 participants