-
Notifications
You must be signed in to change notification settings - Fork 42
Hangout::Getting v4 Moving
Meeting invite: http://kzu.to/yxUxsJ
-
Migration of moq4 repo from Google Code?
- DONE! (Thanks Damian Hickey!): https://github.com/Moq/moq4
-
CI server is UP! (Thanks Damian again!): http://teamcity.codebetter.com/viewType.html?buildTypeId=bt221&tab=buildTypeStatusDiv
-
Bring over two issues which have pending patches in Google Code
- Pending :(
-
Refresher of Moq internals
- Went over the code, a little bit chaotic. Need to put together a couple class diagrams or the like.
-
Pushing to NuGet from CI? YES (TeamCity supports it!)
- Use pre-release "tag"/naming for the CI build: Moq-CI?
- See http://docs.nuget.org/docs/reference/versioning
Mocks have a default pipeline (kinda template for setups). Cloned on first setup of a given call. If no pipeline exists for a call, then default one is run.
Need to get feedback from the community whether the Moq.Source approach to contributions is useful or a waste of time (i.e. people that are capable of contributing already have github accounts and know how to fork/branch/push/send pull requests?). Send patch could generate automatically a NuGet release with just the user's fix (Moq-[git commit hash?]) so that they can move on with their work without having the source in their solution.