rework github strategy to use a more direct method in the common case…

[baronfel]

… of just getting the latest version

[baronfel]

TODO: pagination on the prerelease-case

[forki]

I think there should be no pagination on the prerelease case. If there is no prerelease on the first page then there is no active prerelease.

[baronfel]

ah, and the prerelease logic is really 'latest including prerelease', so we're really just grabbing the first of the 'all releases' page then? that makes that logic simpler as well.

[forki]

Yes we only want the super latest and greatest (and broken) version.
On Aug 28, 2015 20:11, "Chester Husk III" [email protected] wrote:

ah, and the prerelease logic is really 'latest including prerelease', so
we're really just grabbing the first of the 'all releases' page then? that
makes that logic simpler as well.

—
Reply to this email directly or view it on GitHub
#1022 (comment).

[baronfel]

Alright, all better.

[forki]

thanks!

[forki]

sorry. I messed up.

The new bootstrapper doesn't work on prerelease case. It should always get the latest version, but github shows the last released version on top (even if that's older than the latest)

[baronfel]

sounds like we should always get the latest version via the new mechanism, then, and then use that version to compare against if the user requests a prerelease?

so /releases/latest => 1.99.0
then use 1.99.0 to compare against
/releases =>
1.99.0
2.0.0--alpha1million

?