-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 20 Nov 2008 09:43:39 -0500 Brad Buckingham <[EMAIL PROTECTED]> wrote:
> I am, however, a little unclear on the proposed bumping of the API > version. Is it necessary to bump it for each API that added during > the course of a development cycle? Or is it sufficient just to bump > it once for each Spacewalk release? If we bump it for new APIs, do > we also have to bump it for every API modification? > > 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 > many folks will forget to bump the API version as they submit changes > to the APIs, so the might become less reliable/useful. Agreed, during a devel cycle I can't imagine anyone who's relying on the API version for unreleased spacewalk code and needs to know (progrematically) when a new API call is added or a signature changes. 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) Devan Devan - -- Devan Goodwin <[EMAIL PROTECTED]> Software Engineer - Spacewalk / RHN Satellite Halifax, Canada 650.567.9039x79267 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkklhEkACgkQAyHWaPV9my57AQCgmtUO0+xDKgYJasIYFW7x7rqd 2xsAn2VqBq7h1lcUVwFFHoAmyC82doUf =52mC -----END PGP SIGNATURE----- _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
