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

Make TestFx repo CPS based #606

Closed
4 tasks
jayaranigarg opened this issue Apr 22, 2019 · 7 comments
Closed
4 tasks

Make TestFx repo CPS based #606

jayaranigarg opened this issue Apr 22, 2019 · 7 comments

Comments

@jayaranigarg
Copy link
Member

jayaranigarg commented Apr 22, 2019

CPS backlog

This should address other related issues like -

  • Running build.cmd locally results in failure #605
  • [NetCore] Enable support for messages/warnings related to Deployment Items for languages other than English #591
  • Consolidate the adapter and framework nuget packages (with framework being the longterm one) #193
  • Set DisableAppDomain to true, by default
@jayaranigarg
Copy link
Member Author

@cltshivash : Please update this checklist as we uncover/identify more issues that needs to be resolved as part of CPS change.

@parrainc
Copy link
Contributor

@jayaranigarg just wondering... will be PR #411 taken into consideration as part of this feature? Or maybe it's out of scope?

@jayaranigarg
Copy link
Member Author

jayaranigarg commented Apr 25, 2019

@parrainc : We are still working on the design aspect of the CPS change, so mostly PR #411 will not be considered. We are yet to close on that.

@parrainc
Copy link
Contributor

Oh, I see. Just wanted to know if still worth it to invest time on #411 but i think is not.
Thanks for the update. I'll be checking at the issues to see if there more things I can help to get the repo CPS :)

@StingyJack
Copy link

What is a CPS?

@parrainc
Copy link
Contributor

parrainc commented Aug 2, 2019

@StingyJack late but, CPS stands for: Common Project System (check here)

@Evangelink
Copy link
Member

I will move forward by closing this ticket because it seems like most issues have already been handled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants