Doing a v4l-utils-1.0.0 release
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 ?
Regards,
Hans
Quoted 9 lines · On Fri 14 June 2013 09:15:02 Hans de Goede wrote:
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 by me!
Note that the libv4l2rds code is now finalized, so that can be released as well.
Regards,
Hans
I've got a fix for a really bad performance bug, so if you can hold off on doing a release a couple of hours until I can get in front of my Linux box and submit a patch, I would appreciate it.
Thanks,
Devin
Quoted 23 lines · Hans Verkuil
Quoted 9 lines · On Fri 14 June 2013 09:15:02 Hans de Goede wrote:
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 by me!
Note that the libv4l2rds code is now finalized, so that can be released as well.
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 2 lines
Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com
Em Fri, 14 Jun 2013 09:15:02 +0200
Hans de Goede <[email protected]> escreveu:
Quoted 9 lines
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.
So, feel free to bump it to version 1.0.
Regards,
Mauro
Signature · 2 lines
Cheers, Mauro
Quoted 14 lines · On Fri, 14 Jun 2013 10:34:04 -0300 Mauro Carvalho Chehab <[email protected]>…
Em Fri, 14 Jun 2013 09:15:02 +0200
Hans de Goede <[email protected]> escreveu:Quoted 10 lines
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 ?
Quoted 8 lines
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 ?
I'd like to see the polarization stuff fixed because otherwise you can't use sat at all with libdvbv5.
I'll work on the new patches this weekend. I'll hopefully have something today.
I'll see what I can do wrt DiSEqC stuff but that can definitely wait a latter release.
Guy
Hi,
Quoted 20 lines · Guy Martin
Quoted 16 lines · On Fri, 14 Jun 2013 10:34:04 -0300 Mauro Carvalho Chehab <[email protected]>…
Em Fri, 14 Jun 2013 09:15:02 +0200
Hans de Goede <[email protected]> escreveu:Quoted 10 lines
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.
Quoted 8 lines
Quoted 6 lines
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
Hello,
Quoted 1 line · Hans de Goede
So how about taking current master and releasing that as a 1.0.0 release ?
I'm fine with preparing a 1.0.0 release.
But I'm under the impression that the libdvbv5 interface is not polished enough to build a shared library from it. So I'd like to change the autoconf default to false and skip installing the static and shared library.
Any objections?
Thanks,
Gregor
Hello Guy,
Quoted 8 lines · Guy Martin
Can we wait a little bit more like a week max ?
I'd like to see the polarization stuff fixed because otherwise you can't use sat at all with libdvbv5.I'll work on the new patches this weekend. I'll hopefully have something today.
I'll see what I can do wrt DiSEqC stuff but that can definitely wait a latter release.
I saw your patches were merged to v4l-utils. Is there anything else you'd like to have included in a v4l-utils 1.0.0 release?
Thanks,
Gregor
Hi Gregor,
Quoted 2 lines · Gregor Jasny
I saw your patches were merged to v4l-utils. Is there anything else you'd like to have included in a v4l-utils 1.0.0 release?
Nope, that's all I wanted to have for this release.
Next thing will be to work on better diseqc support but it can wait for another release.
Guy
Hello,
Quoted 8 lines · Hans de Goede
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 ?
If nobody objects I'll do a 1.0.0 release this weekend.
Thanks,
Gregor
Hi Gregor,
Let me know when you've branched 1.0.0. I want to merge Bård's work for qv4l2 (openGL support, upcoming audio support and other improvements), but I can't do that until after you made the 1.0.0 branch.
Thanks!
Hans
Quoted 22 lines · Gregor Jasny
Hello,
Quoted 8 lines · Hans de Goede
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 ?
If nobody objects I'll do a 1.0.0 release this weekend.
Thanks,
Gregor--
To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html