On Rails, Ext JS, Netzke, and nomadic lifestyle

Starting with Netzke 1.0 development
August 8, 2015

Guys from PennyMac were extremely generous to offer me an opportunity to do a full month of paid Netzke development so that I could release version 1.0. For the coming 3 months, however, I'll be near-fulltime busy with other client work (React + Rails all the way), so, I plan to get full-steam on Netzke in November, with the deadline set to December 1st. However, this weekend the master on GitHub will already start pointing to, and I'll slowly start some development in my spare time (here's a very rough list of what has to be done). Why the 4-digit version, suddenly? There's a good reason for that.

Note on versioning

I have recently come up with an idea of using a 4-digit versioning schema for each of the 3 Netzke gems (not including the meta gem):

  • 1st digit will increase with each Ext JS major release (as soon as we start supporting it)
  • 2nd digit will increase with each Rails major release (as soon as we start supporting it)
  • 3rd digit will increase with each backward-incompatible changes in the Netzke API, as well as minor releases of Ext JS and/or Rails.
  • 4th digit is for both bug fixes and backward-compatible new features

For example:

  • - Ext JS 5, Rails 4
  • - Ext JS 5, Rails 4, backward incompatible Netzke API
  • - Ext JS 5, Rails 5

  • - Ext JS 6, Rails 4 (or whatever newest Rails we need to support)
  • - Ext JS 6, Rails 5
  • - Ext JS 6, Rails 6, bugfixes

Changes in the first 2 digits will also mean that no backward compatibility of Netzke API is guaranteed, but the details on that, as before, will be provided in the CHANGELOG.

I'll start with supporting Ext JS 5 (and probably Rails 4), as moving to Ext JS 6 is not a priority for PennyMac (nor for my current in-house project, for that matter). You should contact me, however, if your Netzke project needs to support Ext JS 6.

With that said, the meta gem will cut off the 4th digit and still use the 3-digit scheme, and will list its Netzke dependencies using the pessimistic operator in its gemspec, for example:

# in netzke.gemspec
spec.version = "1.2.3"
spec.add_dependency "netzke-core", "~>"
spec.add_dependency "netzke-basepack", "~>"
spec.add_dependency "netzke-testing", "~>"

This will guarantee that specifying the exact netzke gem version in your Gemfile, bundle update will still fetch all (hopefully) backward compatible updates:

gem 'netzke', '1.2.3'

Should something go wrong with the last-digit release of Netzke, you always have the option of getting more specific:

gem 'netzke-core', ''
gem 'netzke-basepack', ''
gem 'netzke-testing', ''

Note, that the 4th digit won't necessarily be synced between Netzke gems.

A word on blogging

I plan to blog and tweet a bit more regularly on the new stuff coming in Netzke, as the 1.0 development progresses. I'll just try to keep the posts more brief and focused, so it doesn't feel like a huge undertaking each time any more.

Please, let me know in the comments what you think (and did I mention the 1.0 roadmap yet?)

comments powered by Disqus

Max Gorin

Web developer and digital roamer since 2008. Author of Netzke. Feminist, atheist, life hacker, and common sense devotee.

Twitter | GitHub | LinkedIn


  1. tutorials (14)
  2. netzke (26)
  3. rails (1)
  4. 0-7 (3)
  5. testing (2)
  6. videos (1)
  7. speaking (5)
  8. 0-8 (5)
  9. productivity (1)
  10. frontend (1)
  11. web-development (1)

By Year

  1. 2016 (1)
  2. 2015 (3)
  3. 2014 (2)
  4. 2013 (4)
  5. 2012 (5)
  6. 2011 (3)
  7. 2010 (6)
  8. 2009 (4)
  9. 2008 (1)