Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Lineups #2572

Closed
harikmenon opened this issue Apr 16, 2016 · 3 comments
Closed

Lineups #2572

harikmenon opened this issue Apr 16, 2016 · 3 comments
Assignees
@anangaur
Labels
Epic Priority:2 Issues for the current backlog.
Milestone
Backlog

Comments

@harikmenon
Copy link

harikmenon commented Apr 16, 2016 •
edited by rrelyea
Loading

Rob updating to include some text:

Support to understand the exact versions that a solution restore chose via an output file.
Ability to take that output, tweak it, and pass it into restore to lock to those versions.

This would provide better support for repeatable builds.
@harikmenon harikmenon self-assigned this Apr 16, 2016
@harikmenon harikmenon added this to the 3.6 Beta milestone Apr 16, 2016
@harikmenon harikmenon added Epic Priority:1 High priority issues that must be resolved in the current sprint. Priority:2 Issues for the current backlog. and removed Priority:1 High priority issues that must be resolved in the current sprint. labels Apr 16, 2016
@harikmenon harikmenon removed this from the 3.6 Beta milestone Apr 19, 2016
@rrelyea rrelyea mentioned this issue May 4, 2016
Open
@natemcmaster natemcmaster mentioned this issue Dec 8, 2016
Open
@rrelyea rrelyea added this to the Future-1 milestone Feb 16, 2017
@natemcmaster natemcmaster mentioned this issue May 11, 2017
Closed
@anangaur anangaur assigned anangaur and unassigned harikmenon May 19, 2017
@nkolev92 nkolev92 mentioned this issue Sep 20, 2017
Closed
@rrelyea
Copy link
Contributor

rrelyea commented Sep 21, 2017

@anangaur - can you please link to your current spec or future spec location in this issue when you are ready to share and get feedback?

@rrelyea rrelyea mentioned this issue Sep 21, 2017
Closed
@anangaur
Copy link
Member

Future spec with some draft content can be found here:

Spec wiki Discussion issue
Enable repeatable builds via lock file #5602

@zhili1208 zhili1208 modified the milestones: Future-1, Backlog Jan 10, 2018
@PatoBeltran
Copy link

Closing this in favor of #6764

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@anangaur anangaur

Labels
Epic Priority:2 Issues for the current backlog.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
5 participants
@PatoBeltran @zhili1208 @rrelyea @harikmenon @anangaur