From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Roadmap for =?utf-8?Q?Guix=C2=A01=2E0?= Date: Thu, 30 Aug 2018 21:34:55 +0200 Message-ID: <87bm9jabs0.fsf@elephly.net> References: <878t5udq9u.fsf@gnu.org> <871sbls435.fsf@gmail.com> <87tvnqipal.fsf@gnu.org> <87lg91on7d.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:60025) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fvSsp-00014z-Tx for guix-devel@gnu.org; Thu, 30 Aug 2018 15:45:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fvSis-0000FT-WE for guix-devel@gnu.org; Thu, 30 Aug 2018 15:35:20 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21072) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fvSir-0000Ev-5J for guix-devel@gnu.org; Thu, 30 Aug 2018 15:35:18 -0400 In-reply-to: <87lg91on7d.fsf@gmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Chris Marusich Cc: guix-devel@gnu.org Hi Chris, > I'm not advocating that we change anything; I'm only advocating that we > should make our stability promise (if any) clear by documenting it. If > you want to know my thoughts about what sort of stability promise we > should provide, I'd be happy to talk about that also, but here I'm only > saying that we should provide a promise. The details of the promise are > less important. > > If you agree, then perhaps we can proceed along the following lines: > > 1) Discuss what our stability promise should be. It might be that we > decide to simply stick with the status quo and document it. But > whatever the result, it should be something that hopefully everyone > agrees on (especially maintainers and contributors). > > 2) Document it. Put it on the website, in the manual, etc. > > 3) Follow it. Mention it in the Contributing section of the manual, the > README, etc., and require people to adhere to it when making changes. > > As a maintainer, what do you think? Does it makes sense for the Guix > project to set expectations by documenting our stability promise? This is difficult. The version jump signalizes that Guix is ready for =E2=80=9Cproductive=E2=80=9D use; it really merely adjusts the version numb= er in accordance with how the community has been using Guix. I=E2=80=99d be wary of putting something more than that in writing. 1.0 me= ans =E2=80=9Cthis works pretty well=E2=80=9D and =E2=80=9Cyou shouldn=E2=80=99t= expect sudden large changes to how this works=E2=80=9D. I=E2=80=99d like to leave the discussion of a stability promise to a time w= hen we decide to maintain a =E2=80=9Cstable=E2=80=9D branch. The other kind of= stability applies only to using Guix as a library, which I don=E2=80=99t think is a v= ery popular use outside of Guix itself. -- Ricardo