Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create historical Rhino releases #1395

Open
p-bakker opened this issue Oct 11, 2023 · 3 comments
Open

Create historical Rhino releases #1395

p-bakker opened this issue Oct 11, 2023 · 3 comments
Labels
distribution Issues related to packaging up Rhino

Comments

@p-bakker
Copy link
Collaborator

p-bakker commented Oct 11, 2023

Rhino have been released from this repo since either version 1.7R4 or 1.7R5 and up to today only had releases for 1.7R5 onwards

Today I added 1.7R4 as a release, in order to host the missing https://github.com/downloads/mozilla/rhino/rhino1_7R4.zip download (recovered it via the wayback machine, checked the checksums)

All releases prior to 1.7R4 (see https://rhino.github.io/releases/ and/or https://udn.realityripple.com/docs/Mozilla/Projects/Rhino/Downloads_archive) were NOT done on Github and their zip artifacts are only available on ftp servers of mozilla (https://ftp.mozilla.org/pub/js/ and https://ftp.mozilla.org/pub/js/older-packages/)

For now they have steadily been available on those mozilla ftp servers, but what if Mozilla decides, just like our documentation, to toss it out?

Hence I think we should create the historical releases on this repo and attach those zip artifacts from the mozilla ftp servers to them, as to have them save

If the releases are created off of the historical tags for those versions, they seem to show up in the right order

All tags from 1.4R3 onwards seem to be there, with the exception of 1.6R7, 1.7R1 and 1.7R2, but I think we could just add those tags (to the correct commit if we can find it) and then all will work the same

After the historical releases are added, the pointers to their artifacts need to be updated as well: https://github.com/rhino/rhino.github.io/blob/main/docs/releases/index.md

@p-bakker p-bakker added the distribution Issues related to packaging up Rhino label Oct 11, 2023
@hfhbd
Copy link

hfhbd commented Oct 12, 2023

Can you please add the original release date to 1.7R4, because GitHub marks it as yesterday? https://github.com/mozilla/rhino/releases/tag/Rhino1_7R4_RELEASE The source code is from 2012-06-12, so I guess this is the original release date.

@p-bakker
Copy link
Collaborator Author

Can you please add the original release date to 1.7R4, because GitHub marks it as yesterday?

Can't alter the date that GitHub sees as the release date, but did now add the original Release Date to the Release Notes

@p-bakker
Copy link
Collaborator Author

Created the historical releases for which a tag already existed, so missing: 1.6R7, 1.7R1 and 1.7R2. So far haven't been able to find on which commit those releases were based

Still to do on the newly created releases:

  • upload the artifacts
  • copy/paste release notes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
distribution Issues related to packaging up Rhino
Projects
None yet
Development

No branches or pull requests

2 participants