![[ChimeraX Issue Tracking System]](/trac/ChimeraX/chrome/site/ChimeraX-icon.svg){kind=icon}
Opened 4 years ago
Closed 4 years ago
#5247 closed defect (fixed)
Make download and older releases pages easier to maintain
| Reported by: | Greg Couch | Owned by: | Greg Couch |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.3 |
| Component: | Infrastructure | Version: | |
| Keywords: | Cc: | Zach Pearson | |
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
With the changes to the download page to emphasis the download page for the platform the web browser is on, it is no longer easy to maintain the older releases page. This needs to be fixed before 1.3 production release is made.
The proposed solution is to put all of the needed information into a JSON file, so the download page will not need to change when a new release is made. Currently, the production release information is hand-coded in the download page, and the daily build information is generated via a cgi-bin script every time the download page is loaded. So the first change will be to put all of that information into a single JSON file after the daily build finish. And way for handling the release candidates will be included. Then the download page can be revised to use the JSON file.
For the older releases page, the information in it will be converted into an analogous JSON file. Then that page can be rewritten to use the JSON file. And when a production release becomes an older release, its JSON information can be copied into the older releases JSON file.
The current plan is for Greg to get the JSON output working with consultation from Zach. And that Zach will do the web page coding with consultation from Greg. This may change.
Added script to generate JSON files for current candidate, daily, and production builds. And manage the JSON for older releases. The older releases JSON is kept under version control.