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

Followup: Better release process #690

Closed
1 of 2 tasks
parasyte opened this issue Jun 3, 2015 · 0 comments
Closed
1 of 2 tasks

Followup: Better release process #690

parasyte opened this issue Jun 3, 2015 · 0 comments
Milestone

Comments

@parasyte
Copy link
Collaborator

parasyte commented Jun 3, 2015

Followup to #508

We should consider the following options:

  • Add a new grunt task to bump the version
  • Release non-versioned build files

The former is pretty obvious, and could be done as part of grunt release.

The latter is more of a political matter. All popular frameworks release build files without a version number in the filename. This allows easy updates for minor versions; bower update is all you need. Or even CDN releases that automatically propagate to CDN users. (But this is dangerous, as any changes may introduce new bugs that break CDN games without warning!)

@parasyte parasyte added this to the 2.2.0 milestone Jun 27, 2015
parasyte added a commit that referenced this issue Jun 27, 2015
parasyte added a commit that referenced this issue Jun 27, 2015
- Makes melonJS usable as a node module.
@parasyte parasyte modified the milestones: 2.2.0, 3.0.0 Jul 26, 2015
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

No branches or pull requests

1 participant