From: Pjotr Prins <pjotr.public12@thebird.nl>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Frederick Muriithi <fredmanglis@gmail.com>
Subject: Re: [PATCH] gnu: Add ldc-1.1.0-beta6
Date: Thu, 19 Jan 2017 11:02:12 +0000 [thread overview]
Message-ID: <20170119110212.GA22866@mail.thebird.nl> (raw)
In-Reply-To: <87y3ykmh23.fsf@gnu.org>
On Mon, Jan 09, 2017 at 03:41:40PM +0100, Ludovic Courtès wrote:
> Overall the patch looks good to me.
>
> One question: We usually avoid packaging software that has no release or
> has an “alpha” or “beta” label. Do you think we could wait for 1.1.0 to
> be officially released? Or are there good reasons why we should not
> wait?
ldc is pretty stable and there are many commits since the last stable
release which are needed. Normally we should support 1.0.0, but since
that is more than 6 months old I think we can skip that. Next round
will be stable 1.1.0 (I am building a git checkout right now because I
need the recent stack trace fix!).
In all I suggest we support 1.1.0-beta6 and then on to 1.1.0 etc. We
can add new beta's on top of that again for those who want it.
Pj.
next prev parent reply other threads:[~2017-01-19 11:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 15:04 [PATCH] gnu: Add ldc-1.1.0-beta6 Frederick Muriithi
2017-01-07 16:32 ` Pjotr Prins
2017-01-09 14:41 ` Ludovic Courtès
2017-01-10 5:55 ` Frederick Muriithi
2017-01-10 14:36 ` Frederick Muriithi
2017-01-12 14:09 ` Ludovic Courtès
2017-01-17 12:58 ` Frederick Muriithi
2017-01-19 12:47 ` Ludovic Courtès
[not found] ` <CALjrZwaJnPN5B5PoLX5Xf56m93nOev5xaydeYYP32sg+88ZzAA@mail.gmail.com>
[not found] ` <CALjrZwbB__c8_VVETcurMxKeP4n3iyN70SpuAexp3jJXAGn8eg@mail.gmail.com>
[not found] ` <CALjrZwY9gNvP_KbmhrR1V+oKxV=RFOCWeqfjQvMZ0t0HX5tEhg@mail.gmail.com>
[not found] ` <CALjrZwapZQtNvdp-KGBUGD6UM34RZxO3Xvqwe=++xGqNvqUE6A@mail.gmail.com>
[not found] ` <CALjrZwavQ0sTw3Ds8ALpYbppvfbNevj7c7vQjqn7uJqY0hqxaA@mail.gmail.com>
[not found] ` <CALjrZwb2iZPcce+vkVoTGfq7dZZ+zbxz3TyxN5L+Uq_cwiO_MQ@mail.gmail.com>
2017-01-19 13:00 ` Frederick Muriithi
2017-01-20 13:33 ` Ludovic Courtès
2017-01-22 9:27 ` Frederick Muriithi
2017-01-28 0:28 ` Ludovic Courtès
2017-01-19 11:02 ` Pjotr Prins [this message]
2017-01-28 6:09 ` Pjotr Prins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170119110212.GA22866@mail.thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=fredmanglis@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).