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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2007/07/12 19:28:04 UTC
[jira] Resolved: (DERBY-2924) Manual copyright topics need to be
updated to current year
[ https://issues.apache.org/jira/browse/DERBY-2924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-2924.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.1.2
Derby Info: (was: [Patch Available])
I committed the patch 2 to docs/trunk with revision 555700 and merged to docs/branches/10.3 docs with 555701. Thx Kim.
> Manual copyright topics need to be updated to current year
> ----------------------------------------------------------
>
> Key: DERBY-2924
> URL: https://issues.apache.org/jira/browse/DERBY-2924
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.3.0.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Blocker
> Fix For: 10.3.1.2
>
> Attachments: DERBY-2924-2.diff, DERBY-2924.diff
>
>
> Although the ditamap files of all the manuals have been updated with the tag "<copyryear year="2004, 2007"/>", the copyright topics all contain the dates "2004, 2006".
> adminguide/radmincopyright.dita:Derby</alt></image></p> <p>Copyright 2004, 2006 The Apache Software Foundation</p> <p> Licensed
> devguide/rdevcopyright.dita:Derby</alt></image></p> <p>Copyright 2004, 2006 The Apache Software Foundation</p> <p> Licensed
> getstart/rgscopyright.dita:Derby</alt></image></p> <p>Copyright 2004, 2006 The Apache Software Foundation</p> <p> Licensed
> ref/rrefcopyright.dita:Derby</alt></image></p> <p>Copyright 2004, 2006 The Apache Software Foundation</p> <p> Licensed
> tools/rtoolscopyright.dita:Derby</alt></image></p> <p>Copyright 2004, 2006 The Apache Software Foundation</p> <p> Licensed
> tuning/rtuncopyright.dita:Derby</alt></image></p> <p>Copyright 2004, 2006 The Apache Software Foundation</p> <p> Licensed
> I would appreciate some feedback on how urgent it is to fix this for the 10.3 release. I'm sorry not to have noticed it before.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.