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 577123 - Add Pulse Support to Docs
Add Pulse Support to Docs
Status: RESOLVED FIXED
Product: epiphany-extensions
Classification: Deprecated
Component: general
master
Other Linux
: Normal normal
: ---
Assigned To: epiphany-extensions-maint
epiphany-extensions-maint
Depends on:
Blocks:
 
 
Reported: 2009-03-28 20:42 UTC by Paul Cutler
Modified: 2009-05-24 15:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Adds Pulse support to docs (388 bytes, patch)
2009-03-28 20:44 UTC, Paul Cutler
committed Details | Review
Fix XML (648 bytes, patch)
2009-05-08 03:59 UTC, Paul Cutler
none Details | Review

Description Paul Cutler 2009-03-28 20:42:50 UTC
This patch adds support for the GNOME Docs Project's Pulse application to track documentation updates by adding a <releaseinfo> tag.
Comment 1 Paul Cutler 2009-03-28 20:44:23 UTC
Created attachment 131593 [details] [review]
Adds Pulse support to docs

This patch was built against SVN trunk as I did not see a 2.26 branch.  Pulse status is left in "review" until Bug 438806 is committed / released.
Comment 2 Christian Persch 2009-03-28 21:01:05 UTC
The branch for 2.26 is the same as for 2.24, "gnome-2-24". 
Ok to commit to gnome-2-24; for trunk wait for the ok from the trunk maintainers.

Comment 3 Paul Cutler 2009-03-28 21:37:48 UTC
I do not have GNOME SVN commit access, will need someone to commit.  Thank you.
Comment 4 Xan Lopez 2009-04-01 18:08:56 UTC
OK, stupid question, should I commit that as-is or changing 2.26 for something else or...? Does it need to be updated for each release?
Comment 5 Paul Cutler 2009-04-05 14:18:06 UTC
This patch can be committed as is.

Each release recycle, if documentation needs to be updated, the <releasetag> is changed to show it (planning, review, candidate, etc).  This first patch just ass the <releasetag> so we can track it's status in Pulse.
Comment 6 Xan Lopez 2009-04-16 06:57:17 UTC
Thanks, committed in trunk.
Comment 7 Paul Cutler 2009-05-08 03:59:09 UTC
Created attachment 134241 [details] [review]
Fix XML

It was brought to my attention that I had a bad XML tag.  This patch fixes it, and the XML passes:

xmllint --noout --xinclude --noent --postvalid epiphany-extensions.xml

I apologize for the bad patch.  This new patch was build against git branch.
Comment 8 Simos Xenitellis 2009-05-24 15:24:55 UTC
I committed the fix on master,

commit 7a5c5257c130b4662059d2f2d2f93fb064d6dd54
Author: Paul Cutler <pcutler@foresightlinux.org>
Date:   Sun May 24 16:19:23 2009 +0100

    Fixed documentation XML validity issue.
    
    help/C/epiphany-extensions.xml: Fixed documentation validity issue.
    Related to #577123, comment #7.

Details at
http://git.gnome.org/cgit/epiphany-extensions/commit/?id=7a5c5257c130b4662059d2f2d2f93fb064d6dd54

I hope it is fine with the maintainer.