[
https://issues.apache.org/jira/browse/HBASE-25520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17373108#comment-17373108
]
Duo Zhang commented on HBASE-25520:
-----------------------------------
After some investigating, I think we could just use downloads.apache.org and
archive.apache.org to place the CHANGES.md and RELEASENOTES.md?
We will upload CHANGES.md and RELEASENOTES.md to dist.apache.org. So for the
current release, we could see them on downloads.apache.org.
https://downloads.apache.org/hbase/2.4.4/CHANGES.md
And we will link to previous CHANGES.md in the above CHANGES.md, then we could
use archive.apache.org.
https://archive.apache.org/dist/hbase/2.3.0/CHANGES.md
A possible problem is that, once we want to fix a CHANGES.md for old releases,
I do not know if there is a way to change the content on archive.apache.org...
Thanks.
> Exclude CHANGES and RELEASENOTES files from source control
> ----------------------------------------------------------
>
> Key: HBASE-25520
> URL: https://issues.apache.org/jira/browse/HBASE-25520
> Project: HBase
> Issue Type: Task
> Components: build, community
> Reporter: Nick Dimiduk
> Priority: Major
>
> Over on the thread [Project management (JIRA fix version tracking) is in
> crisis
> |https://lists.apache.org/thread.html/r8db075fd974de32a90174be2db106ef710cf38cfde9ea9071fda4152%40%3Cdev.hbase.apache.org%3E],
> one of the suggested improvements to our process is to remove the CHANGES
> and RELEASENOTES files from version control. To accomplish this, we'll need to
> * delete existing files from existing branches
> * modify the release automation to not commit this files
> * find someplace to deliver these files on the web
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
