Internal versioning and releasing

gistfile1.txt

In response to:

Josh Susser - The @rubyrogues topic for tomorrow is Versioning and Release Process. Any questions or particular things you'd like to see us address?
Mark McSpadden - @joshsusser @rubyrogues The versioning/release dance between self maintained services and gems. (When you own the service and the gem.)
Josh Susser - @markmcspadden can you expand on that? I don't quite understand what you're asking. @rubyrogues

--

I've experienced several situations where there's an internal service 
(usually Rails, sometimes Sinatra or Rack) that has a corresponding gem. 
Often I or whoever wrote the service maintains both the service and the gem.

You would think this makes for easier maintenance, versioning, and releases...
I mean...you know everything about both...but you also know everything about both.
 I follow the standard major.minor.patch...but usually end up never feeling great 
about either side of it.

Maybe it's the patch version that's problem here. Often the patch numbers could vary
greatly between the gem and the service...but it "feels" like 1.2.1 of the gem
"should" match to 1.2.1 of the service.

I may just be over thinking/obsessing here...thanks for letting me talk 
through this a bit.

- Mark