Devan Goodwin wrote:
The reason that I ask is that we don't bump the Spacewalk version for
every change that is submitted to it. I also suspect that over time
Why?
many folks will forget to bump the API version as they submit changes
to the APIs, so the might become less reliable/useful.
This is what I have on my mind. To prevent forgeting on bump up api version.
IMO we should up the API version once and only once per spacewalk
release. (either right before it goes out the door, or right after the
last release is made, actually the latter sounds better) Even if there
are API bugfixes post-release they won't be changing the signature for
calls and thus no need for a minor version increase. (if I understand
the purpose of API version anyhow)
Hmm, can be. If we make it part of branch process, it will work.
So right after freezing release into separate branch, bump up apiversion
in master.
So what to do with major and minor then? What about increase minor
number every spacewalk release and increase major number for every
"stable release" i.e. the release, from which satellite will be made.
--
Miroslav Suchy
RHN Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
