![[ChimeraX Issue Tracking System]](/trac/ChimeraX/chrome/site/ChimeraX-icon.svg){kind=icon}
Opened 5 years ago
Last modified 5 years ago
#3332 assigned defect
Get sample code from relevant branch
| Reported by: | Eric Pettersen | Owned by: | Greg Couch |
|---|---|---|---|
| Priority: | moderate | Milestone: | |
| Component: | Documentation | Version: | |
| Keywords: | Cc: | Greg Couch | |
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
Original mail:
The CGI script that generates the sample-code zip file (URL: https://www.cgl.ucsf.edu/chimerax/cgi-bin/bundle_sample.zip ; file: plato:/usr/local/projects/chimerax/www/preview/cgi-bin/bundle_sample.zip), uses the "develop" branch from git, and therefore has not picked up the changes to the sample code. Should we temporarily change that to "release/v1.0"? Is there a better solution?
Proposed solution:
Won't we always have the problem of which branch to use if they're different? Maybe the right way is to include the branch in the URL and then have the link in the docs be parameterized by "make".
Note:
See TracTickets
for help on using tickets.
An alternate solution would be to put the sample code in a bundle and update the bundle as needed. After the 1.0 release, developers should rarely use the develop branch version unless they are developing against the next major (incompatible) version.