tinker_james

@tinker_james@programming.dev

• ⁨Comment⁩ on ⁨How do you balance rapid iteration and merging/upgrading?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Context:

  I’m a dev that consumes company wide libraries, not an author of such libraries. So the following comes from that perspective.

  A couple questions:

  1. Is development and consumption of your library happening in parallel? It sounds like you use the users to vet new features or major changes… is that correct? (They are iterating with you and reporting back on issues or desired changes)
  2. Is your library made up of a group of isolated components? Or is it a library that does one or two major things and so a breaking change literally changes the whole of what the library does?
  3. How are the consumers of your library when it comes to adopting changes? Do they readily do it? Is there a good bit of inertia?

  My thoughts:

  First off, SemVer is definitely going to be important. Also, it sounds like you’re working toward API stabilization which is going help iterating in the future.

  My idea 1:

  If your library is made up of several isolated components, what about doing major releases (ex 2.x.x -> 3.x.x) more frequently? Only include a small subset of breaking changes for one or two components rather than jamming a whole bunch in there just because it’s a “major version release”. The result is you could move quickly and iterate while also minimizing the impact on ALL of your users every release. Some of your users may be able to upgrade to the latest without having to touch much or any of their code.

  My idea 2:

  Do frequent major release (ex 2.x.x - 3.x.x) but always start with an “alpha” release that early adopters could implement and provide feedback on. This would shield the majority of your consumer’s code from having to iterate frequently but would also require you to enlist a group of committed early adopters that are diligent about iterating their code as often as you release.

  Feedback on the original option 1 and 2

  Option 1

  This could work if your users are excited about your releases. But, it could result in people NEVER upgrading because it’s too much work to do so. (I’ve seen this happen. No one upgrades until they absolutely have to.)

  Option 2

  Depending on the size of your company, this will be a lot of work for you and will slow you down. If you’re using your users to vet out new features, then everyone is going to have to iterate frequently (like you said) if experimental changes don’t work out.