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.

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

Add NuGet badge #17946

Merged
merged 1 commit into from
Dec 8, 2015
Merged

Add NuGet badge #17946

merged 1 commit into from
Dec 8, 2015

Conversation

supergibbs
Copy link
Contributor

No description provided.

@cvrebert
Copy link
Collaborator

Were we gonna use NuGet with v4? From folks in the discussion, I thought it was considered quasi-deprecated by ASP.next (or whatever) in favor of Bower/npm, and thus kinda an interim thing?

@supergibbs
Copy link
Contributor Author

My understanding from @mdo in slack was it would continue to be supported. Plus you merged in #17214 😃

@cvrebert
Copy link
Collaborator

Hmm, well v4-dev doesn't currently have a nuget/ folder, so things are gonna break when v4 becomes master..

@supergibbs
Copy link
Contributor Author

True, I'll make a PR so MyGet will continue to work when that happens. Will be a v3 branch for a while as well for bugfixes? If so, we can set up another build in MyGet to maintain that too.

@cvrebert
Copy link
Collaborator

Will be a v3 branch for a while as well for bugfixes?

Yeah. Once v4 hits master, the old master (v3) will get moved to another branch.

@mdo mdo added this to the v4.0.0-alpha.2 milestone Dec 8, 2015
mdo added a commit that referenced this pull request Dec 8, 2015
@mdo mdo merged commit 46fa32e into twbs:v4-dev Dec 8, 2015
@supergibbs supergibbs deleted the NuGet_badge_v4 branch December 23, 2015 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants