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 652350 - Formalize the Documentation release process
Formalize the Documentation release process
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: Documentation
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Yawar Amin
Tom Bullock
Depends on:
Blocks:
 
 
Reported: 2011-06-11 12:24 UTC by Geert Janssens
Modified: 2018-06-29 22:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Geert Janssens 2011-06-11 12:24:15 UTC
The GnuCash program has a release process that is more or less formal, although maybe not completely documented.

The GnuCash documentation however is left out of that. This enhancement request is opened to discuss what is missing to have a semi-formal, and documented release process for the GnuCash documentation, so that the release process can be carried over if one release manager can for whatever reason no longer perform the releases.
Comment 1 Geert Janssens 2011-06-11 12:34:48 UTC
From bug 535424 comment 9 :

> ...With the next GC release, if it's ok, I would like to also release a newer
> version of documentation due to a lot of modifications and closed bug since
> the last release. I dont't know how to make a new release but I'm willing to
> learn but that's another topic...

The release schedule of the documentation is completely independent of the release schedule of the program. So if you would like a release now, we could organize that already before 2.4.7 is released.

Perhaps 2 releases are in order: one for the 2.2 branch and one for the 2.4 branch.

I can take care of tagging the releases if you like and I can put the new documentation on the GnuCash website (linked from the documentation page.

But I believe I don't have permission to upload the release tarballs to sourceforge, which would be required for distributions to pick up a new release.

What is also missing is a template for a news item on the website for documentation releases. That would be useful as well, as I wouldn't want to write a complete news message with each new documentation release.
Comment 2 Geert Janssens 2011-07-02 16:44:55 UTC
While releasing gnucash-docs 2.2.2 and 2.4.1 I created some notes for release managers [1]. These notes are an adaptation of the notes to release the code [2].

In my opinion, this is sufficient to document the documentation release process. If anyone wants to add something or has comments, feel free to modify the wiki page directly.

[1] http://wiki.gnucash.org/wiki/Documentation_Release_Process
[2] http://wiki.gnucash.org/wiki/Release_Process
Comment 3 John Ralls 2018-06-29 22:59:05 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=652350. Please update any external references or bookmarks.