[
https://issues.apache.org/jira/browse/DERBY-6911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Pendleton resolved DERBY-6911.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.13.1.1
I believe we've completed the 10.13 release successfully,
so I'm marking this issue resolved.
Many thanks to the community for their support, and
particular thanks to Rick for helping me many times as
I wandered through the process.
Overall, the current Release Manager documentation is thorough
and accurate, although it is a complex process.
The documentation is made more complex because we have
retained detailed information about how to make releases of
old Derby codelines.
Although that is a nice body of knowledge, I'm not sure I see
the value in retaining it, and I do believe that the Release Manager
documentation in the wiki would be dramatically easier to follow
if it **only** described the current release process.
But for the most part I didn't rototill the RM pages during the
process; I tried to keep my edits to those necessary to bring it up to date.
A particular challenge is that several parts of the RM process
interact with broader Apache mechanisms, and the broader
Apache mechanisms continue to evolve and their documentation,
too, is out of date. This is just a problem with software in general,
I'm afraid.
Anyway, there may not be another Derby release for a little
while, but at least I know somewhat more about the tools and
techniques that are used to make such a release.
> Updates related to producing the 10.13 release
> ----------------------------------------------
>
> Key: DERBY-6911
> URL: https://issues.apache.org/jira/browse/DERBY-6911
> Project: Derby
> Issue Type: Improvement
> Reporter: Bryan Pendleton
> Assignee: Bryan Pendleton
> Fix For: 10.13.1.1
>
>
> This JIRA issue was used to track the miscellaneous work I did while
> producing the 10.13.1. release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
