[
https://issues.apache.org/jira/browse/DERBY-7177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029574#comment-18029574
]
Richard N. Hillegas commented on DERBY-7177:
--------------------------------------------
These are the steps for retiring Derby, as I understand them:
o Update the Derby STATUS page, recording the vote to retire Derby.
o Update the <shortdesc> element of doap_Derby.rdf to note that Derby has been
retired.
o Add a disclaimer to the Derby landing page
(https://db.apache.org/derby/index.html), explaining that Derby is no longer
actively maintained, bugs are not being fixed, new releases are not being
published.
o Add a similar disclaimer to the Derby download tab
(https://db.apache.org/derby/derby_downloads.html), explaining that Derby has
been retired, bugs are not being fixed, downloads are available on an as-is
basis.
o Add a similar disclaimer to the landing page of the Derby wiki
(https://cwiki.apache.org/confluence/display/DERBY/FrontPage), explaining that
Derby is no longer being actively maintained.
o Open an INFRA ticket, requesting that Derby's JIRA, website, wiki, and
mailing lists be put in read-only mode.
o Send an ASF-wide announcement that Derby has been retired.
> Retire Derby
> ------------
>
> Key: DERBY-7177
> URL: https://issues.apache.org/jira/browse/DERBY-7177
> Project: Derby
> Issue Type: Task
> Components: Web Site
> Affects Versions: 10.18.0.0
> Reporter: Richard N. Hillegas
> Assignee: Richard N. Hillegas
> Priority: Major
>
> Retire the Derby project, putting it in read-only mode, making it clear that
> no one actively maintains the project going forward.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
