db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Commented: (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
Date Wed, 20 Oct 2010 13:13:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922948#action_12922948
] 

Kim Haase commented on DERBY-4851:
----------------------------------

Thanks for doing this, Rick. I think, though, that parameterizing the copyright year in the
Getting Started timestamps is not too useful, since we will want to get an entirely new timestamp
at each release, not just fix the year. Release 10.7 did not exist last February. (It doesn't
exist now, either, but it's closer. I have previously updated the docs on the trunk after
the release to correct the date and release.)

Also Mamta changed the timestamp output to be more user-friendly; it now looks like this,
with the user's local time zone --

Tue Oct 12 14:16:07 EDT 2010

instead of this:

2010-02-11 21:56:41.744 GMT


> 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
>         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.


Mime
View raw message