Bug 891168 - RFE: add finer-grained control of revisions to add_revision command
Summary: RFE: add finer-grained control of revisions to add_revision command
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Publican
Classification: Community
Component: publican
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeff Fearn 🐞
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-02 06:26 UTC by Ruediger Landmann
Modified: 2013-07-04 05:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-04 05:26:07 UTC
Embargoed:


Attachments (Terms of Use)

Description Ruediger Landmann 2013-01-02 06:26:22 UTC
Description of problem:
The add_revision command only increments the release number; it would be useful to be able to specify that a revision should increment the major or minor revision number instead. The revnumber switch allows the writer to override this behaviour, but requires the writer to investigate the Revision History to determine what the next value should be.

Most documentation changes are best reflected by an increase in minor revision; this should be the default.

Version-Release number of selected component (if applicable):
3.0

How reproducible:
100%

Steps to Reproduce:
1. run add_revision on a book in the source language
2. inspect the Revision_History.xml file in the source language
  
Actual results:
The revision number takes the form x.y-z. The value of z is incremented by add_revision unless overridden by the --revnumber option

Expected results:
Writer should be able to specify next x, y, or z without reviewing the file contents. Increments should default to y.

Comment 1 Jeff Fearn 🐞 2013-03-08 03:18:51 UTC
Doesn't --revnumber cover this?


Note You need to log in before you can comment on or make changes to this bug.