Skip to content
This repository has been archived by the owner on Nov 19, 2017. It is now read-only.

nunit.xamarin 3.6.1 release #53

Merged
merged 2 commits into from
Mar 14, 2017
Merged

nunit.xamarin 3.6.1 release #53

merged 2 commits into from
Mar 14, 2017

Conversation

ChrisMaddock
Copy link
Member

NOT READY TO MERGE - This will be for @rprouse to merge, after reviewing and releasing nunit/nunit.xamarin#90 (which I hope to complete the work for tonight!)


I know historically we've only put the 'core products' on the download page - but I thought it might give the Xamarin runners a little more exposure, adding them here. What do people think - @rprouse @nunit/core-team?

@rprouse
Copy link
Member

rprouse commented Mar 14, 2017

I am okay with including this in the downloads. The Xamarin runners are getting more traction recently. @CharliePoole?

@CharliePoole
Copy link
Member

I still think this is experimental. Do you guys? Maybe a separate section?

@rprouse
Copy link
Member

rprouse commented Mar 14, 2017

I would be fine with a separate section.

@ChrisMaddock
Copy link
Member Author

Happy to put it in a separate section.

How should we title it? I'm not sure about 'experimental' - is there a path towards making it un-experimental? I've considered this ready for use, have I been mistaken?

@CharliePoole
Copy link
Member

Perhaps it's "Development". 😄

One of the things I would like to see the new core team do is to decide on "categories" for projects. I see this as very important because being a "core" or "production" product (whatever we call it) means we promise to users that we will keep supporting it in the future. Compare that to a "contributed" project like the junit transform - I don't think we are under any obligation to support it if the contributor should disappear. The teamcity extension is similar, although I'm sure JetBrains isn't going to disappear.

Anyway, without discussing the merits of any particular cases, I hope that shows why I think it's important to know whether a project is "core" or "developmental". We have to agree on terms eventually, of course, but to me "developmental" means it's on the way to "core", while "experimental" means we might cancel the whole project at any point.

Obviously, none of this is of any use unless users know about the distinctions.

Given that it's such a big deal, maybe you should just merge what you have and we can discuss it further in the context of #55. @rprouse?

@rprouse
Copy link
Member

rprouse commented Mar 14, 2017

I'm okay with just merging for now and making the larger decision in #55.

@rprouse rprouse merged commit 8a92878 into master Mar 14, 2017
@rprouse rprouse deleted the xamarin branch March 14, 2017 19:47
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