[Bug 756424] New: docs: documentation not committed
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Mon Oct 12 02:49:55 PDT 2015
https://bugzilla.gnome.org/show_bug.cgi?id=756424
Bug ID: 756424
Summary: docs: documentation not committed
Classification: Platform
Product: GStreamer
Version: git master
OS: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gst-plugins-bad
Assignee: gstreamer-bugs at lists.freedesktop.org
Reporter: florin.apostol at oregan.net
QA Contact: gstreamer-bugs at lists.freedesktop.org
GNOME version: ---
running make distclean && autogen.sh && make will create a bunch of modified
files in docs folder. Why is the gstreamer version updated in the "Back to
development" commit but the documentation updated only when the new release tag
is updated? According to the continuous integration principles, everything
should be kept up to date and at the moment of release only a tag needs to be
applied.
Is this process documented somewhere? I would like to understand the reason for
updating documentation only at the end of the development cycle.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list