From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: device-mapper development <dm-devel@redhat.com>,
Christophe Varoqui <christophe.varoqui@opensvc.com>,
Hannes Reinecke <hare@suse.de>,
Benjamin Marzinski <bmarzins@redhat.com>,
mathieu.tl@gmail.com
Subject: Re: Next release plans?
Date: Mon, 11 Apr 2016 19:09:43 +0200 [thread overview]
Message-ID: <570BDA57.7040606@gmail.com> (raw)
In-Reply-To: <561531AF.4080907@gmail.com>
On 10/07/2015 04:52 PM, Xose Vazquez Perez wrote:
> Christophe Varoqui wrote:
>
>> Mathieu Trudel-Lapierre wrote:
>>>
>>> I'm curious, are there any plans to cut a new formal release tarball in
>>> the near future?
>>>
>>> The 0.5.0 release was done more than a year ago, and it seems like there
>>> are quite a lot of bug fixes which may benefit everyone. In Ubuntu, I've
>>> so far been cherry-picking patches as necessary, but it's obvious this
>>> can't scale well (and that then important patches may go unnoticed).
>
>> yes, you can expect a formal release before summer holidays.
>> I still have to catch up with the patches my inbox before.
>
> Any progress ? There are a lot of SuSE/Red Hat pending patches.
Christophe, how's it going?
Hannes, is there new SuSE patches for upstream?
-thanks-
next prev parent reply other threads:[~2016-04-11 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 14:52 Next release plans? Xose Vazquez Perez
2016-04-11 17:09 ` Xose Vazquez Perez [this message]
2016-04-18 9:42 ` Christophe Varoqui
2016-04-18 11:10 ` Hannes Reinecke
2016-04-18 21:57 ` Xose Vazquez Perez
2016-04-18 22:22 ` Xose Vazquez Perez
2016-04-19 11:47 ` Ritesh Raj Sarraf
2016-05-10 16:39 ` [PATCH Debian] kpartx: increase retries was " Xose Vazquez Perez
2016-05-11 17:36 ` Christophe Varoqui
-- strict thread matches above, loose matches on Subject: below --
2015-06-02 16:46 Mathieu Trudel-Lapierre
2015-06-03 7:44 ` Christophe Varoqui
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570BDA57.7040606@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=mathieu.tl@gmail.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox