[CDRIVER-527] On github incorrect information in section "Building from Release Tarball" Created: 10/Feb/15 Updated: 08/May/15 Resolved: 08/May/15 |
|
| Status: | Closed |
| Project: | C Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1.5 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Tatjana | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
On github incorrect information in section "Building from Release Tarball" Everywhere is mentioned information about version 1.1.1, but as I know the latest tarball you have is 1.1.0. Or link to tarball is broken. "The most current release is 1.1.1 which you can download here. mongo-c-driver-1.1.1.tar.gz." |
| Comments |
| Comment by Tatjana [ 02/Mar/15 ] |
|
Thank you. It would be grate to have same link(that does not change) for latest stable and changing links for each branch. I think that would fix problem. But it is just advice. Thank you for explanation. |
| Comment by Mira Carey [ 26/Feb/15 ] |
|
Hi, The information on github is reflective of the README available from whatever branch you're looking at. And as part of our release bump, we upgrade all of the various links to point to point to the next unstable dev release, bumping again when we tag. So those links should resolve if you look at the latest release tag, rather than master. I'm still up in the air on exactly how I want to manage this (maybe change the default branch for github, maybe a readme that mentions the unstable version numbers), but that's the work around for now. Regards, |