After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 756424 - docs: documentation not committed
docs: documentation not committed
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal normal
: 1.7.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-10-12 09:49 UTC by Florin Apostol
Modified: 2015-10-12 12:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Florin Apostol 2015-10-12 09:49:55 UTC 
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.
Comment 1 Tim-Philipp Müller 2015-10-12 10:04:47 UTC 
It is updated and uploaded during the development cycle as well, whenever someone feels it makes sense to do so. Otherwise it just adds noise.

What are you looking for exactly here?
Comment 2 Florin Apostol 2015-10-12 10:06:23 UTC 
I expected to not have a dirty git folder after I run "make distclean && autogen.sh && make" on master.
Comment 3 Tim-Philipp Müller 2015-10-12 10:08:54 UTC 
Ah, right. I didn't get that initially for some reason, only once I force a docs update.

commit a6d89901feefcd29ec7eafeb54a37b8950f706f0
Author: Tim-Philipp Müller <tim@centricular.com>
Date:   Mon Oct 12 11:07:32 2015 +0100

    docs: update to git
    
    https://bugzilla.gnome.org/show_bug.cgi?id=756424
Comment 4 Florin Apostol 2015-10-12 12:20:04 UTC 
I synced with master and still have dirty files in docs folder. For example
docs/plugins/gst-plugins-bad-plugins.args

@@ -1869,11 +1869,11 @@
 </ARG>
 
 <ARG>
 <NAME>GstDvbSrc::diseqc-source</NAME>
 <TYPE>gint</TYPE>
-<RANGE>[G_MAXULONG,7]</RANGE>
+<RANGE>[-1,7]</RANGE>
 <FLAGS>rw</FLAGS>
 <NICK>diseqc source</NICK>
 <BLURB>(DVB-S/S2) Selected DiSEqC source. Only needed if you have a DiSEqC switch. Otherwise leave at -1 (disabled).</BLURB>
 <DEFAULT>-1</DEFAULT>
 </ARG>

and docs/plugins/gst-plugins-bad-plugins.hierarchy
@@ -1,19 +1,12 @@
 GObject
   GInitiallyUnowned
     GstObject
       GstAllocator
         GstAllocatorSysmem
-        GstVdpVideoAllocator
-        GstWlShmAllocator
-      GstAudioRingBuffer
-        GstAudioSinkRingBuffer
-        GstAudioSrcRingBuffer
       GstBus
       GstClock
-        GstSystemClock
-          GstAudioClock
       GstControlBinding
       GstControlSource
       GstElement
         GstAggregator
           GstAudioAggregator
Comment 5 Tim-Philipp Müller 2015-10-12 12:31:12 UTC 
Yes, I don't think the generated docs output is always stable. Feel free to work on that and propose a patch if it bothers you :)
Comment 6 Tim-Philipp Müller 2015-10-12 12:31:53 UTC 
Oh, also, it will vary from system to system depending on what plugins get compiled.