Skip to content
This repository has been archived by the owner on Oct 5, 2018. It is now read-only.

Initial checkin for supporting MaxVersion in SemVerStrategyState #117

Closed
wants to merge 1 commit into from

Conversation

dlethin
Copy link

@dlethin dlethin commented May 23, 2015

Next step is to define some version strategies that make use of it

…t step is to define some version strategies that make use of it
@ajoberstar
Copy link
Owner

Overall, this code looks good, but I'd like to play out the idea of reusing NearestVersionLocator some more. I'll throw together my own PR for this and we can see what the best next steps will be.

@ajoberstar
Copy link
Owner

Just created #118 for my alternate impl. Still need to push up the tests for it. However, I don't think that approach is going to work very well. Without understanding what the branches are being used for, it's hard (maybe impossible) to know whether parallel development should override the nearest.

@kknd22
Copy link

kknd22 commented Jul 15, 2016

any movements on this? i think this might solve one of my issue:
#202

@ajoberstar
Copy link
Owner

See my comment on #202 .

@ajoberstar
Copy link
Owner

I still want to address this, but given how long this PR's been open, I'm going to close. The original issue is still open.

@ajoberstar ajoberstar closed this Nov 26, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants