Earn badges and make progress
You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
How does the selection of a release track influence the updates for products that dont have a track
Greetings,
im currently trying out the rather new "Release Track" option for the standard and premium licenses, and have a question pertaining to impact of the choice of said release track for a product.
In my example, im testing the release track function for Confluence (Cloud), having set the track to "Bundled". Meanwhile, my Jira is still set to "Continuous", Jira being on a "Free" license currently. See also attached screenshot:
My question now is: How are the changes that relate to the general "Atlassian Cloud" rolled out under this context?
- Will they be bundled together with the changes that will be rolled out to my Confluence Cloud?
- Or will Atlassian Cloud changes be rolled out continuously, just as they always have?
The importance of this question lies within the fact that we need to write a potential validation concept, and while the release track function helps creating a more practical cadence of re-validations of the Confluence Cloud, we still might need to always check for updates that are being rolled out to the Atlassian Cloud, that could affect the validated status of our Confluence Cloud.
1 answer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.