Update list of mirrored releases, add more instructions to release guide. #117
Conversation
|
changes look fine to me but I'm just starting to get familiar with release process |
| <programming-language>Python</programming-language> | ||
| <programming-language>R</programming-language> | ||
| <programming-language>SQL</programming-language> | ||
| <programming-language>JDBC</programming-language> |
site/release-process.html
Outdated
|
|
||
| <p>Make sure to also remove the unpublished staging repositories from the <a href="https://repository.apache.org/">Apache Nexus Repository Manager</a>.</p> | ||
|
|
||
| <p>When removing older releases, also update <code>js/download.js</code> to indicate the release is not mirrored |
There was a problem hiding this comment.
could we expand on When removing older releases happens?
I think given major.minor.patch, the previous patch release is archived when a newer one in the same major.minor is released?
ie, 2.1.3 released, 2.1.2 archived
There was a problem hiding this comment.
This is already sort of covered by the existing text:
Spark always keeps two releases in the mirror network: the most recent release on the current and
previous branches.
That doesn't seem to really correspond to the current mirrored releases (and with the expectation of the Hive tests that were added in 2.2), though, so maybe we should update that policy.
There was a problem hiding this comment.
right, that doesn't seem to match the ASF mirror behavior now
felixcheung
left a comment
felixcheung
left a comment
There was a problem hiding this comment.
is there removal on https://dist.apache.org/repos/dist/release/spark/ automatic, by ASF mirror policy, or manual?
I see 2.3.0 now when 2.3.1 is up. maybe there's a time delay
|
It is manual. I did not remove 2.3.0 but maybe I should given the updated policy I just sort of made up. |
|
I see.. |
|
I'm merging this. We can continue to tweak the release guide as we find new things. |
3 participants
No description provided.