GNOME Bugzilla – Bug 756424
docs: documentation not committed
Last modified: 2015-10-12 12:31:53 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.
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?
I expected to not have a dirty git folder after I run "make distclean && autogen.sh && make" on master.
Ah, right. I didn't get that initially for some reason, only once I force a docs update.
Author: Tim-Philipp Müller <email@example.com>
Date: Mon Oct 12 11:07:32 2015 +0100
docs: update to git
I synced with master and still have dirty files in docs folder. For example
@@ -1869,11 +1869,11 @@
<BLURB>(DVB-S/S2) Selected DiSEqC source. Only needed if you have a DiSEqC switch. Otherwise leave at -1 (disabled).</BLURB>
@@ -1,19 +1,12 @@
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 :)
Oh, also, it will vary from system to system depending on what plugins get compiled.