You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2011/01/12 19:28:47 UTC

[jira] Updated: (DERBY-4851) Parameterize documentation sources so that release-time variables (like copyright year and release id) can be plugged in when we build a release

     [ https://issues.apache.org/jira/browse/DERBY-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-4851:
----------------------------------

    Fix Version/s: 10.7.1.1

> Parameterize documentation sources so that release-time variables (like copyright year and release id) can be plugged in when we build a release
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4851
>                 URL: https://issues.apache.org/jira/browse/DERBY-4851
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.7.1.1
>
>         Attachments: derby-4851-01-aa-copyrightYear.diff, derby-4851-02-aa-shortVersionNumber.diff, derby-4851-03-aa-longReleaseID-and-subversionRevision.diff
>
>
> Right now there are a number of strings which have to be updated in the user guides every time that we cut a branch or generate a release candidate. We should parameterize these strings so that the build script can fill them in. Probably we will have to use the ant substitution task for this because there is no obvious way to do this via DITA.
> These are the variables I am aware of. Please let me know if there are others:
> Latest copyright year (currently 2010)
> 2 part version number (e.g., 10.7) (this is plugged into the ij script output, among other uses)
> 4 part version number (e.g. 10.7.1.0)
> subversion revision number (e.g. 1000400)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.