2010/10/1 Mateusz Loskot <[email protected]>
> To all interested package maintainers, share your comments and
> vote for your favourite option please.
>
I believe whatever the version numbering, you feel comfortable with, is fine
for me, as long as the soname version is consistent with that and easy to
maintain.
So, for instance, if you feel that the next version should be 3.5.0, fine,
let us name 3.5.0 (and the soname version would be either 3.5.0 or 3.5).
After a few patches, it would become 3.5.4, for instance (and, depending on
the soname version numbering choice, the soname version would become either
3.5.4 or remains 3.5; that latter choice implies that no ABI change has
occurred, which seems reasonable).
Then, we have some API change, and the new version becomes 4.0.0.
And so on.
That way, it is easy for everyone to understand, easy to maintain, and there
are no some somewhat rigid guidelines to follow, which would require hours
to understand before any new release is to be done.
Just my 0.02$.
Denis
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Soci-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/soci-users
