A few weeks. Unfortunately Atlassian are putting the pressure on by announcing these vulns at the same time as releasing 6.2, so more people than would normally are keen to get on the 6.2.0 release.
I agree with Norman, I almost never take the .0 version of a new major release.
Hey John, not sure if this is Jamie's preferred means to recieve/answer update questions like this, but I know he is usually pretty quick to turn things around.
I would log the request on his public issue tracker so other folks can vote, and jamie can communicate back to users.(example from 6.1 compatibility https://jamieechlin.atlassian.net/browse/JBHV/fixforversion/17901)
My stock answer for plugins is 4 to 6 weeks after Atlassian releases a new version because there are hundreds of plugins that need to be updated. Even atlassian supported plugins are not done before a product is released.
This timeframe is also about the time that Atlassian will release a point release (ie fixing issues), so I generally end up avoiding the initial problems caused by new releases.
Even though developers can get early releases, they really need to wait until Atlassian does it production release for the final adjustments and testing. Then developers need to schedule the time to work on their plugins since plugins are not their primary job.
I really wish there was a separate area on answers for announcements and the marketplace had a better view for the matrix compatability across all plugins where admins could register their interests and see all the plugins at once. Then the developer would be able to put a note on their progress.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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