Skip to content

Hypergrid v3.2.1
Compare
Choose a tag to compare
@joneit joneit released this 03 May 12:31
· 32 commits to master since this release
v3.2.1
a556956
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.

Minor version update

This is a "patch release" (fixes/improvements); it is interface-backwards-compatible with all v3...

Contents

  1. Anonymous column calculator bug (see PR #786)
  2. New: ./umd folder in npm module

As noted in the previous release (v3.2.0)...

Worth repeating:

Change regarding Versioning

Going forward and starting with [the v3.2.0] 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 semantics 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 will tell you). After all, during a PR merge, git applies the 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.

umd folder

The npm module now includes a ./umd folder which contains the same two build files found on the GitHub CDN (fin-hypergrid.js and fin-hypergrid.min.js).

Pre-bundled build files

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

Assets 2
Loading