Stale versioning and ambiguity in Feedback Assistant

[ilterbilguven]

Hi @ryzngard,

I have been using this plugins for almost two years. And I think there are two main problems with this package.

• The versions are stale. Some of them are past 6 months. I have an automation for this repo to build them into packages. Because of stale versioning, it's hard to maintain it. At least, each commit should include a version bump. Bumping the patch version is not a big deal.

• Apple Unity Plug-Ins does not have any place in Feedback Assistant. Is it going to be in "Developer Tools & Resources" or "Developer Technologies & SDK"? Probably Developer Technologies & SDK. But If I have a problem with CoreHaptics, what should I choose? "Something else not on the list" is not a good option. It won't get enough attention, because there is a pile of different things in that category. This plugin will exist for a long time and it deserves to have its own category.

[ryzngard]

Thanks for commenting @ilterbilguven, I'm glad you have been using the plugins for so long!

For versioning, we snap versions with releases. Every commit won't result in a version bump, but when a release is finalized it should. We have 27-beta setup now for the upcoming release matching the WWDC announcement. Let me know if you have any problems with versioning on that branch.

For feedback, I would encourage you to file issues here if it's related to the plugins themselves. If you need help filing general feedback for CoreHaptics not related to the plugins I can help track down the appropriate Feedback Assistant category for you.

[ilterbilguven]

Hi @ryzngard ,

What do you mean by snapping versions with releases? I mean if you fixed a thing, a patch version bump is ok. For example, my MR #47 is accepted. But CoreHaptics is 1.3.1 for 1.5 years. At least this should have caused 1.3.2 release. I don't think there is a new feature is coming for CoreHaptics, so that's why I'm calling versioning here as stale.

For feedback, I am for using here as well, but at README.md, "Feedback" takes you to the Feedback Assistant, which causes an ambiguity IMHO.

[ryzngard]

What do you mean by snapping versions with releases? I mean if you fixed a thing, a patch version bump is ok. For example, my MR #47 is accepted. But CoreHaptics is 1.3.1 for 1.5 years. At least this should have caused 1.3.2 release. I don't think there is a new feature is coming for CoreHaptics, so that's why I'm calling versioning here as stale.

Yes, I need to go and update the package versions in the beta branch. I missed this one.

For feedback, I am for using here as well, but at README.md, "Feedback" takes you to the Feedback Assistant, which causes an ambiguity IMHO.

Ah that's right! Thank you, I'll make sure to update the readme. We didn't have issues on the repo open so feedback assistant used to be the only way.