Update release-policy.md #591
Conversation
Add Project Download Page policy to legal release policy document.
|
Nice. |
sebbASF
left a comment
sebbASF
left a comment
There was a problem hiding this comment.
Please start a new line for each sentence in a paragraph. They will be merged together (unless separated by a blank line).
This makes diffs clearer, and subsequent changes simpler.
Make each sentence start on a line to make it easier to edit.
|
@sebbASF Thanks for the suggestion. I've made each sentence a new line. |
Update announcement requirements to include explicit reference to the Project Download Page.
|
@sebbASF please review. Anything else needed now? |
| materials outside the development community. | ||
| Projects SHALL provide one or more Project Download Pages as part of their web site. | ||
| Projects with multiple sub-projects MAY provide multiple Project Download Pages | ||
| that correspond to sub-projects. |
There was a problem hiding this comment.
I don't think this sentence is needed, given that the surrounding statements make it clear that there can be more than one project download page.
There was a problem hiding this comment.
This is the only mention of sub-projects on the page, and I think it's appropriate to mention.
There was a problem hiding this comment.
What is a sub-project? AIUI, PMCs have may have multiple projects. They do not have sub-projects.
If a PMC starts with one project, and then adds another, do they both become sub-projects? I think the wording is unnecessary and confusing.
|
|
||
| Projects SHALL publish official releases and SHALL NOT publish unreleased | ||
| materials outside the development community. | ||
| Projects SHALL provide one or more Project Download Pages as part of their web site. |
There was a problem hiding this comment.
Need to check with Infra here - AIUI, there has been some talk of standardising download pages; these would not be part of the project website.
Also, emphasising PROJECT might be confusing for podlings. I'm not sure it is necessary to coin a new phrase; they are just download pages
There was a problem hiding this comment.
Some talk of standardizing pages has been on the agenda for years. Once infra has something concrete we can discuss further.
Emphasizing Project Download Page is to avoid confusion with pages such as downloads.apache.org/project/release/artifact which we have seen is confusing.
There was a problem hiding this comment.
It is unclear what is being asked of Infra here. There have been no changes to the release policy. Please take this to a mailing list.
There was a problem hiding this comment.
@clambertus Nothing is being asked of infra. There are no changes proposed to the release policy.
This is a clarification because of some projects' confusion about what belongs in announcements.
|
Changes to Legal's release policy need to be approved by Legal. I do not understand the purpose of these changes, as the process and requirements are already documented in this page and in https://infra.apache.org/release-distribution.html. What is the problem we are trying to solve for here? |
|
@clambertus The purpose of these changes is to clarify what a download page is. Many announcements of releases contain links to downloads.apache.org which is clearly a "download page" since the word download is in the URL. |
|
@clambertus These are not changes to policy but clarification. If Legal wants to weigh in on whether the changes correctly reflect policy, that would be great. But no policy change is being suggested here. |
|
I would like approval from Legal. Clarification or not, this is a suggested change to their content. This should be discussed on list on legal-discuss@ |
5 participants
Clarify existing Project Download Page policy in legal release policy document.