Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-835

Split the XTS documentation from a single developers guide to two developer guides, one in /docs for product/project and one in /XTS/docs for project only

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Obsolete
    • Icon: Major Major
    • 4.15.2
    • None
    • None
    • None

      The summary sort of says it really, not certain on the timeframe required so I dropped it into the 4.15 timeframe, please feel free to discuss and move the fix version as I appreciate it is close to the deadline!

      I have already done this for JTA/JTS based on Marks split so can do the same for XTS but I do not know what is community and what is common so would need some clear pointers on this if you want me to split the doc.

            [JBTM-835] Split the XTS documentation from a single developers guide to two developer guides, one in /docs for product/project and one in /XTS/docs for project only

            Andrew Dinn added a comment -

            As of AS7 the XTS 1.0 code is no longer being built so there is no need to maintain this split in docs for the 4.15 branch.

            Andrew Dinn added a comment - As of AS7 the XTS 1.0 code is no longer being built so there is no need to maintain this split in docs for the 4.15 branch.

            Andrew Dinn added a comment -

            punted to next minor release

            Andrew Dinn added a comment - punted to next minor release

            Andrew Dinn added a comment -

            The amount of work required for this is probably only very small since the differences between the 1.1 product release and the 1.1/1.0 community release are documented as small notes describing how 1.0 differs. I think the best way to make this split would be to retain one version and find some way of pre-processing the xml to remove the 1.0-specific content. I am punting this to the next minor point release so we can decide whetehr to do this or to produce two versions. n.b. if we don't want to support 1.0 any more (probably a good thing) then we can just remove the 1.0 specific comments.

            Andrew Dinn added a comment - The amount of work required for this is probably only very small since the differences between the 1.1 product release and the 1.1/1.0 community release are documented as small notes describing how 1.0 differs. I think the best way to make this split would be to retain one version and find some way of pre-processing the xml to remove the 1.0-specific content. I am punting this to the next minor point release so we can decide whetehr to do this or to produce two versions. n.b. if we don't want to support 1.0 any more (probably a good thing) then we can just remove the 1.0 specific comments.

              rhn-engineering-adinn Andrew Dinn
              thjenkin@redhat.com Tom Jenkinson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: