Hi Kinto Soft,
When looking at official explanation:
"Subversion ALM for JIRA has been archived due the lack of free time to support it properly. The new JIRA Data Center architecture has a big impact on the current design among other improvements like support for tracking merges etc. that cannot be afforded."
In my opinion this should not be a reason to suddenly remove the plugin from the marketplace. I totally understand that there is no much time to to support but keeping this on marketplace is not breaking instances. Plugins should be available for some time even that are no longer compatible with the latest versions. Many users are still using older versions of JIRA. Why you did not wanted to keep it?
I do not agree with that. Of course if you know what you need it is OK however on Marketplace you have more information about the related version. In your official documentation you added only last version that do not even say which JIRA version is supported.
In general people are using UPM and in this there is a link to the Marketplace not official site. When clicking on this they see that plugin was archived (Dejan screenshot) and no additional info why.. when.. is there any other plugin.. how to cleanup now the instance or transition to other plugin...
Only when googling someone can find this question or your official site where he can find answers.
In addition.. I can say that the official information was created few days ago and plugin was not available on the marketplace for a while.
In my opinion plugin should be on the marketplace until all people will stop using it .. and who knows maybe you are not having time right now but in half a year or a month you will be able to figure out how to make it compatible..
Lastly I can say also that JIRA Data Center is not replacing JIRA and there is no need to make plugin compatible for this new offering that was by the way officially announced yesterday.. not a month ago..
It has been un-archived with new and very important changes:
1. It is not longer supported. I know some companies would preffer a supported commercial version, but I discarded it after thinking about it carefully: with Atlassian providing commercial FishEye and free JIRA Subversion plugin for Server and with the new free and commercial offer from a 3rd party company for Cloud, there were not too much market share.
2. OpenSource. There are too many active instances (+700 for ALM and +400 for old Plus) and it was very unfair discontinue it without proving an alternative. So, OpenSource seems a good solution as current users can fix bugs and contribute to new features/enhancements.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot