From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Gregor Jasny <gjasny@googlemail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Upcoming v4l-utils 1.6.0 release
Date: Fri, 10 Oct 2014 17:34:02 -0300 [thread overview]
Message-ID: <20141010173402.7095e5fb@recife.lan> (raw)
In-Reply-To: <54319E45.3050906@googlemail.com>
Hi Gregor,
Em Sun, 05 Oct 2014 21:38:45 +0200
Gregor Jasny <gjasny@googlemail.com> escreveu:
> Hello,
>
> On 04/10/14 16:22, Mauro Carvalho Chehab wrote:
> > Em Tue, 30 Sep 2014 18:29:26 +0200
> > Hans de Goede <hdegoede@redhat.com> escreveu:
> >> About the 1.6.0 release, please do not release it until the series
> >> fixing the regression in 1.4.0 with gstreamer which I've posted
> >> today. A review of that series would be appreciated. If you're ok
> >> with the series feel free to push it to master.
>
> I pushed the changes to master ans built a Debian package with the
> changes. The bug reported verified that it properly fixed the bug.
While waiting for this package to get enough carma to merge it on F21,
I was wandering that, as we don't quite follow http://semver.org/
versioning, we should document it. So, I wrote the enclosed patch.
Please review.
Regards,
Mauro
README: better document the package
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
diff --git a/README b/README
index a9f8089..f12b37d 100644
--- a/README
+++ b/README
@@ -1,20 +1,124 @@
v4l-utils
---------
-Linux V4L2 and DVB API utilities and v4l libraries (libv4l).
+Linux utilities and libraries to handle media devices (TV devices,
+capture devices, radio devices, remote controllers).
+
You can always find the latest development v4l-utils in the git repo:
-http://git.linuxtv.org/v4l-utils.git
+ http://git.linuxtv.org/v4l-utils.git
+Those utilities follow the latest Linux Kernel media API, as documented
+at:
+ http://linuxtv.org/downloads/v4l-dvb-apis/
-v4l libraries (libv4l, libdvbv5)
---------------------------------
+----------
+versioning
+----------
-See README.libv4l for more information on libv4l, libv4l is released
-under the GNU Lesser General Public License.
+The v4l-utils doesn't quite follow the release versioning defined
+at semver.org.
+Instead, since version 1.0, it uses:
-v4l-utils
+ MAJOR.MINOR.PATCH
+
+Where:
+
+ MINOR - an odd number means a development version. When
+ the development is closed, we release an even
+ numbered version and start a newer odd version;
+
+ MAJOR - It is incremented when MINOR number starts to be
+ too big. The last change occurred from 0.9.x to 1.0.
+
+ All numbers start with 0.
+
+All versions have their own tags, except for the current
+deveopment version (with uses the master branch at the git tree).
+
+The PATCH meaning actually depends if the version is stable
+or developent.
+
+For even MAJOR.MINOR versions (1.0, 1.2, 1.4, 1.6, ...)
+
+ PATCH is incremented when just bug fixes are added;
+
+For odd MAJOR.MINOR versions (1.1, 1.3, 1.5, 1.7, ...)
+ PATCH is incremented for release candidate versions.
+
+API/ABI stability:
+-----------------
+
+There should not have any API/ABI changes when PATCH is incremented.
+
+When MAJOR and/or MINOR are incremented, the API/ABI for the
+libraries might change, although we do all the efforts for not
+doing it, except when inevitable.
+
+The TODO files should specify the events that will generate
+API/ABI breaks.
+
+---------------
+media libraries
+---------------
+
+There are currently three media libraries defined at /lib directory,
+meant to be used internally and by other applications.
+
+libv4l
+------
+
+This library is meant to be used by applications that need to
+talk with V4L2 devices (webcams, analog TV, stream grabbers).
+
+It can be found on the following directories:
+ lib/libv4l1
+ lib/libv4l2
+ lib/libv4l-mplane
+ lib/libv4lconvert
+
+See README.libv4l for more information on libv4l.
+
+The libv4l is released under the GNU Lesser General Public License.
+
+libdvbv5
+--------
+
+This library is meant to be used by digital TV applications that
+need to talk with media hardware.
+
+Full documentation is provided via Doxygen. It can be built,
+after configuring the package, with:
+ $ make doxygen-run
+
+It is possible to generate documentation in html, man pages and pdf
+formats.
+
+The documentation is also available via web, at:
+ http://linuxtv.org/docs/libdvbv5/
+
+It can be found on the following directory:
+ lib/libdvbv5
+
+The libdvbv5 is released under GPL version 2.
+
+
+libv4l2rds
+----------
+
+This library provides support for RDS radio applications.
+
+It can be found on the following directory:
+ lib/libv4l2rds
+
+The libv4l is released under the GNU Lesser General Public License.
+
+---------
+Utilities
---------
+
+The utilities are stored under /util directory.
+
The (for now for v4l-utils private use only) libv4l2util library is
released under the GNU Lesser General Public License, all other code is
released under the GNU General Public License.
prev parent reply other threads:[~2014-10-10 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140925213820.1bbf43c2@recife.lan>
2014-09-27 10:57 ` Upcoming v4l-utils 1.6.0 release Gregor Jasny
2014-09-27 11:54 ` Mauro Carvalho Chehab
2014-09-30 15:20 ` Gregor Jasny
2014-09-30 16:29 ` Hans de Goede
2014-10-04 14:22 ` Mauro Carvalho Chehab
2014-10-05 19:38 ` Gregor Jasny
2014-10-06 0:25 ` Mauro Carvalho Chehab
2014-10-10 20:34 ` Mauro Carvalho Chehab [this message]
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=20141010173402.7095e5fb@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=gjasny@googlemail.com \
--cc=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.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.
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 NNTP newsgroup(s).