unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: preparing the next release v0.15.0
Date: Tue, 19 Jun 2018 09:25:17 +0200	[thread overview]
Message-ID: <CAE4v=pjQNGXRBQf_P6knqkR-gLi8AGy4yr5J3r=yiGcfgPo2Ew@mail.gmail.com> (raw)
In-Reply-To: <87tvpzvntv.fsf@elephly.net>

[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]

Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2018. jún. 19., K,
0:17):

> Hi Guix,
>
> I wrote almost 6 days ago:
>
> > Here are a bunch of things that we should look into:
> >
> > * Outstanding patches.  There are many patches in the queue at
> >   guix-patches[1] that we should go through, comment on, and/or apply
> >   before the release.  Who would like to join a task force to do that
> >   together?  Let’s pick 5 patches each and review them so that we can
> >   either comment to ask for changes or to apply them.
>

This week I'm on vacation. I can start helping with the patches the next
week.
Are there any to priority ones?



> >
> >   [1]: https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix-patches
> >
> > * breakage since the last core-updates merge.  Since the long overdue
> >   merge of the “core-updates” branch we have a few serious problems on
> >   i686 (e.g. the gst-plugins-base package) and armhf.  Who would like to
> >   lead an effort to investigate and fix these problems?  (Note: you
> >   obviously don’t need to fix them yourself, just keep track of these
> >   things and coordinate with others who investigate them.)
> >
> > * collecting new features and big changes in NEWS.  The NEWS file
> >   already lists some of the changes that the next release would provide
> >   compared to 0.14.0, but we all know that there are more.  Who would
> >   like to take charge of the NEWS file?  This involves asking people for
> >   changes they would really like to be mentioned and coordinating with
> >   other volunteers to search through all commits since v0.14.0 to find
> >   noteworthy changes.
> >
> […]
> > Did I miss anything?  Who wants to help?
>
> We aim for a release on June 30, 2018.  Unfortunately, so far nobody has
> come forward to help us coordinate one of these three tasks.
>
> Any volunteers?
>
> --
> Ricardo
>
>
>

[-- Attachment #2: Type: text/html, Size: 2669 bytes --]

  parent reply	other threads:[~2018-06-19  7:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13 21:07 preparing the next release v0.15.0 Ricardo Wurmus
2018-06-14  5:46 ` Pjotr Prins
2018-06-14  8:24   ` Ricardo Wurmus
2018-06-14 19:46     ` Pierre Neidhardt
2018-06-15  9:42     ` Ludovic Courtès
2018-06-14  9:14   ` Clément Lassieur
2018-07-02  9:44     ` Ludovic Courtès
2018-07-02 15:25       ` Efraim Flashner
2018-07-03 19:43         ` Ludovic Courtès
2018-07-03 20:24           ` Ricardo Wurmus
2018-07-04  7:28           ` Ludovic Courtès
2018-07-02 15:29       ` Nils Gillmann
2018-06-15  9:53 ` Ludovic Courtès
2018-06-15 13:11   ` Ricardo Wurmus
2018-06-18 20:31 ` Ricardo Wurmus
2018-06-18 22:44   ` Pierre Neidhardt
2018-06-19  1:49   ` Kei Kebreau
2018-06-19  7:25   ` Gábor Boskovits [this message]
2018-06-19 12:36   ` Marius Bakke
2018-06-19 12:48     ` Julien Lepiller
2018-06-19 14:32       ` swedebugia
2018-06-20 20:45       ` Ricardo Wurmus
2018-06-20 18:38     ` Kei Kebreau
2018-06-20 20:33       ` Nils Gillmann
2018-06-20 21:10         ` Ludovic Courtès
2018-06-21  1:05           ` Kei Kebreau
2018-06-21 10:45             ` Ricardo Wurmus
2018-06-20 21:11       ` Marius Bakke
2018-06-20 21:55       ` swedebugia
2018-06-21  1:06         ` Kei Kebreau

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='CAE4v=pjQNGXRBQf_P6knqkR-gLi8AGy4yr5J3r=yiGcfgPo2Ew@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).