Date: Wed, 21 May 2014 22:31:20 +0200 From: Erik Cederstrand <erik+lists@cederstrand.dk> To: Alfred Perlstein <bright@mu.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Royce Williams <royce@tycho.org> Subject: Re: [GSoC] Machine readable output from userland utilities Message-ID: <AD9084B7-EDC5-4561-BE04-F29A4B8A83C0@cederstrand.dk> In-Reply-To: <537CD1EE.2000708@mu.org> References: <49E9736E-AD14-4647-8B15-30603D01360C@mail.bg> <91FE2526-F21C-42AB-BECB-058DBA975A9E@cederstrand.dk> <537C2993.1060206@mu.org> <E9594D41-64FE-4957-98FD-4E52BCCB2598@cederstrand.dk> <CA%2BE3k91obr3AVGEme5sVU2NQy0scmeT6beN6E9WUz5a6gUnMbQ@mail.gmail.com> <537C63DF.1090402@mu.org> <8DDBACB5-749B-4660-B1DE-F2EE51033D96@cederstrand.dk> <537CD1EE.2000708@mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Den 21/05/2014 kl. 18.18 skrev Alfred Perlstein <bright@mu.org>: > That sounds reasonable. Is there a link to the specifics we can have? I'm surprised that I couldn't find anything written in the Developers' = Handbook or elsewhere. =46rom what I gather, it's along the lines of: * Don't break the API in the duration of a major release. Additional = features may be added in minor releases. * Mark an API for deprecation in the next major release, and remove it = in the next major release after that. * API changes should try to adhere to POLA. * The policy is not strict and may be violated for e.g. security = reasons. For convenience, a utility could announce the API version in the output = (something comparable to symbol versioning for shared libs), but a = simpler solution would simply require scripts to check which FreeBSD = release they are running on before making assumptions about the XML/JSON = output. Just like Python scripts that support different Python versions = must handle version differences manually. Erik=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AD9084B7-EDC5-4561-BE04-F29A4B8A83C0>