-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[Package Issue]: Move Neotys.NeoLoad to Tricentis.NeoLoad #66937
Comments
I would actually leave the 8.0.0 manifest in the Neotys folder, with the incorrect metadata. Specifically, I would update everything except for the publisher, even going so far as to add AppsAndFeaturesEntries with the incorrect publisher value Then, I would create a copy of the 8.0.0 manifest in the Tricentis folder, and make sure the AppsAndFeaturesEntries and all other metadata is correct. Although I haven’t verified, this should cause anyone on Neotys.NeoLoad < 8.0.0 to be updated to Neotys.NeoLoad 8.0.0; But, once updated, the AppsAndFeaturesEntries should now match the new package - Tricentis.NeoLoad, and new versions will follow the updates from the new publisher folder |
I agree with your suggestion. This process would help considerably. Our longer-term solution is likely to be a combination of: I've seen this come up a few times now. I'm not sure where the best place is to document this as a recommended practice. Maybe it's time for an F.A.Q. What are your thoughts on this? |
I think an FAQ would be good; I think special topics of interest would be Publisher changes / acquisitions as mentioned here, Zip support, Common causes of “No installed package found matching criteria” when trying to upgrade, What is an ARP Entry, Issues with Unknown package version, issues with Disambiguation of side-by-side installs (VC++ / Dotnet), etc. If there were a central place like an FAQ that we could reference to all of the “common issues” that we see, it would be great. I propose we use our Blind Pair Programming group on Gitter to gather opinions, then I can create a draft markdown file and we can get it published |
Just leaving this here - Validated the transition is working as expected:
|
Please confirm these before moving forward
Category of the issue
Other
Brief description of your issue
Neotys has been acquired by Tricentis and new versions (
7.8.1
onwards) of Neotys.NeoLoad haveTricentis
in the publisher field instead ofNeotys
.Should I move this 8.0.0 manifest from
Neotys.NeoLoad
toTricentis.NeoLoad
(and update its metadata) and add newer versions in the new directory? Or should I add the newer versions in the old directory?Secondly (if moderators approve the move), what about the old versions (
7.3
to7.8.1
) present in Neotys.NeoLoad directory? Should we get rid of them or should they remain in the old directory? They might be a cause of confusion for the user as then two same packages would be under different publisher directories.Steps to reproduce
.
Actual behavior
.
Expected behavior
.
Environment
.
Screenshots and Logs
No response
The text was updated successfully, but these errors were encountered: