From: Hans de Goede <hdegoede@redhat.com>
To: Guy Martin <gmsoft@tuxicoman.be>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Doing a v4l-utils-1.0.0 release
Date: Mon, 17 Jun 2013 08:34:50 +0200 [thread overview]
Message-ID: <51BEAE0A.7060706@redhat.com> (raw)
In-Reply-To: <20130615123337.1ba83c63@borg.bxl.tuxicoman.be>
Hi,
On 06/15/2013 12:33 PM, Guy Martin wrote:
>
> On Fri, 14 Jun 2013 10:34:04 -0300
> Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
>
>> Em Fri, 14 Jun 2013 09:15:02 +0200
>> Hans de Goede <hdegoede@redhat.com> escreveu:
>>
>>> Hi All,
>>>
>>> IIRC the 0.9.x series were meant as development releases leading up
>>> to a new stable 1.0.0 release. Lately there have been no
>>> maintenance 0.8.x releases and a lot of interesting development
>>> going on in the 0.9.x, while at the same time there have been no
>>> issues reported against 0.9.x (iow it seems stable).
>>>
>>> So how about taking current master and releasing that as a 1.0.0
>>> release ?
>>
>> Fine for me.
>>
>> There are 5 patches floating at patchwork to improve the DVB-S
>> support with different types of DiSEqC, but applying them would break
>> library support for tvd. So, they won't be applied as-is, and Guy
>> needs to take some other approach. As he is also planning to add
>> support there for rotors, it looks ok to postpone such changes to a
>> latter version.
>
> Can we wait a little bit more like a week max ?
Sure, I was just trying to see what people think about doing a 1.0.0
release. I see no reason to rush it.
Regards,
Hans
next prev parent reply other threads:[~2013-06-17 6:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 7:15 Doing a v4l-utils-1.0.0 release Hans de Goede
2013-06-14 8:51 ` Hans Verkuil
2013-06-14 12:19 ` Devin Heitmueller
2013-06-14 13:34 ` Mauro Carvalho Chehab
2013-06-15 10:33 ` Guy Martin
2013-06-17 6:34 ` Hans de Goede [this message]
2013-07-25 12:36 ` Gregor Jasny
2013-07-25 12:40 ` Guy Martin
2013-06-17 14:59 ` Gregor Jasny
2013-08-01 18:28 ` Gregor Jasny
2013-08-02 6:46 ` Hans Verkuil
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=51BEAE0A.7060706@redhat.com \
--to=hdegoede@redhat.com \
--cc=gmsoft@tuxicoman.be \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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