Move RawURL ahead of Github

[isuruf]

Sometimes the github tags don't really match conda versions and checking using RawURL earlier is better.

[CJ-Wright]

Do you have an example of this? (I don't doubt you, I'm just curious)

[isuruf]

I was trying to make https://github.com/conda-forge/tbb-feedstock/blob/master/recipe/meta.yaml bot friendly.
Their github tags are like 2018_U4.

[isuruf]

Issue is in the script, you are replacing the current conda version with the new github tag, right? This implies that the github tag has to be in the same format as the conda version. (There were a few adjustments made to the github tag in update_upstream_versions.py)

With RawURL, we can just check incrementing the conda version and if that fails try the github tags. We can also advice recipe maintainers to use the conda version in {% set version = "2018.0.3" %} and somehow derive the actual github tag 2018_U3 using jinja. This way we can just increment 2018.0.3 to 2018.0.4 in update_upstream_versions.py with RawURL.

[CJ-Wright]

Hmm, we had a similar issue with the LAMMPS PR conda-forge/staged-recipes#5790 so we might try to make some consistent policy. I had advocated the other way around, for version to be the version number put out by the upstream developers and then have jinja2 templating to convert it to the proper conda syntax. This way we could properly convert the version over by rendering the meta.yaml. I am open to the other way however.

[isuruf]

Issue is that we don't know how the github tags should be sorted. For example in tbb, it doesn't find 2018_U4 and finds 2018 as the latest. In LAMMPS, it doesn't find an appropriate version at all.

Therefore I think the best idea is to have version be the conda version and the upstream version should be calculated from it.

[CJ-Wright]

I'm on board with that.

[isuruf]

#166

[isuruf]

Fixed in #166