Skip to content

Hypergrid v3.2.0
Compare
Choose a tag to compare
@joneit joneit released this 17 Nov 19:03
· 39 commits to master since this release
v3.2.0
9d19656
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Note regarding the CDN release

The 3.2.0 pre-bundled build files were not published to the CDN as intended on 17-Nov-2018 along with the github repo and npm releases. This was due to an errant symlink which was rejected by the github pages build process, which event unfortunately went unnoticed. The CDN build was finally published on 29-Nov-2018. We regret the delay and apologize for any confusion that may have resulted.

Minor version update

This is a "minor version update," meaning it's interface-backwards-compatible with v3.1.* but introduces some new methods.

Contents

  1. Add mouse event details (see PR #773)
  2. Add Base.prototype.versionAtLeast (see PR #777)
  3. Add Registry.prototype.make (see PR #775)
  4. Add images.setTheme: Support for themeable SVG images (see PR #772)
  5. Bump version number (#778)
  6. Update README.md (#779)
  7. Resolve jsdoc compilation issue (#781)

Change regarding Versioning

Going forward and starting with this release, we shall bump the minor version number (middle tupple of version number) on any new functionality per npm SEMVER.

Previously we were often just bumping the patch number (last tupple), but patches are meant for bug fixes that do not introduce any new functionality. The interface for a minor version bump is non-breaking/backwards compatible. It may however be expanded with new but optional parameters; just so long as it doesn't break existing code.

Change regarding pull requests

Going forward and starting with this release, we shall be switching over to the single-item-per-PR paradigm (where "item" is a bug fix or new feature implementation).

Previously we were putting an entire release's items into a single branch/PR with separate commits per item. This was easy to work with for me as the only active contributor because commits therein could be based on earlier commits without intermediate merges. Besides not being conducive to multiple contributors, however, it was difficult (impossible really) to get anyone to code review a big PR. Doing so requires reviewing each commit one by one. GitHub conversations are better supported at the PR level rather than at the commit level.

This change in strategy should make reviewing less daunting and hopefully we'll get more feedback before merging.

A final merge-to-master PR for the release shall bump the version number and update the README. A summary of the constituent PRs shall be listed in the PR description field (as well as being plainly visible in the commit list below the description).

Regarding rebasing

Constant rebasing is not necessary just to move the commit ahead of develop before the merge. Although the resulting git log --graph railroad diagrams end of with leap-frogging commit paths, they are still easily comprehensible. Only rebase when there are merge conflicts (which GitHub checks will tell you). After all, during a PR merge, git applies the exact same merge algorithms as would be performed in a rebase with no conflicts.

Published to npm

This release has been published as a module to the npm registry.

Pre-bundled build files

A bundled build of this release is available on the CDN.

Assets 2
Loading