-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi there,
you may have noticed, nagios-plugins released a new version, which has a tag of a new major release (2.0). This looks like they are trying to start a version number competition. I`m proposing a new version scheme which could look like: <year>.<month>[.bugfixrelease] If you think this looks very familiar ... yes it`s used by ubuntu and may others. What maybe the benefits of a complete different release scheme: * there will probably no version number races between existing forks (which is totally nonsense) * we can better identify, if a plugin is from our fork or no - this might help when we get bugreports/complaints, especially when forks are more diversing on code base Just my 2 euro cents. Have a nice day, Jan. - -- Never write mail to <[email protected]>, you have been warned! - -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++ - ------END GEEK CODE BLOCK------ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJTKtM4AAoJEAxwVXtaBlE+7R8P/iXnVQARQFI7Si5Nm/Cv+l3a vXDdIR7VBdTow+nFQ5rlPOmoE555q+atqr0fljRGanFdNsMwaNo5PWsmQDT/5cNp Uq+59jVkZHtJ5KvUtwrO9Mhsiry0AmHDGvlV4UfLg0n/wqe3ef7xBwi7JsjaR3ln qbPFTCN9Rod7Y88Ro6NLfRfX//cUWVES+v2nqjT7B6luL+TR/Oyq5CAzRtcga/FU vOJNx/+P3efW2nfYYG+Vh3YJzCE/KR2UOi5QAx2Oiii8q08Gu5IcrVywO8emV0en hecM/wdUkCrfou1v1EkHX5IzZyPYaSLrJqmupXT2WEVrLMv2MnD0dmnHkijoOThB QkuDLXyw27n/TP27g4TUER8reeNXyKMSZJbCLNFTewa9R3Xt/03y8DjB9JR8VRoW wmMs0m9OC5wBy/KokMfLXI7s2b7o4MKSeH2I6c4U98TFQwLtUKZFlK/a0Rouxa+q OCjZI8N1Rx6hagTfJyyMl3bIXu81XEPqCkJtT5aMeioZJE5aAc2BGc9RtS1fj+8A kgALdaYeCqqVhHYNlthUiGNMc6K+Fgcoi1mHxCHTSczOZ4HJsjTZ4o4Kw8xiqlQs zJs/vmSFatLgjslcxtyd6zVt1JEgE+tUaWR5z0PT/AJLCdM0OhZevBT/OKRVmuDS f3psjsaE5yt0AwlkVRK9 =15kD -----END PGP SIGNATURE-----
