nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Release availability

Karie Kelly1

Do you know when JIRA 6.0 and Confluence 5.0 will be officially released and supported? Thus, driving when plugins are being supported. For example Adaptavist Content Formatting macro on OnDemand has issues working with the current beta version that is on the site and they have just stated it's not yet supported (which makes sense)

Accepted answers

MatthewC

I was at the London Atlassian user group last night (http://www.meetup.com/UK-Atlassian-Community/events/98533332/) where Atlassian told us that Confluence 5.0 will be 19th Feb and Jira will be release in March, "when it's ready"

All comments

MatthewC

best to watch the early access program which will show you releases before they become official.

http://www.atlassian.com/software/jira/download-eap

http://www.atlassian.com/software/confluence/download-eap

Also read the release notes

https://confluence.atlassian.com/display/DOC/Confluence+5.0-Beta2+Release+Notes

Atlassian never official commit to release dates but you do get a feeling one is coming soon-ish, especially as they are telling the plugin developers to get ready https://developer.atlassian.com/display/CONFDEV/Preparing+for+Confluence+5.0

They also tend to upgrade onDemand a few weeks before they do the main release.

With Adaptavist, you have to remember that if it's a free macro, they will upgrade it when they have time. they always seem to have a lot of commercial work which will always take precedent over upgrading free macros. I'm sure they would take a commision though!

Karie Kelly1

Thanks for the info. I only inquire about Adaptavist because it is one of the few that Atlassian is enabling on OnDemand; therefore, it becomes a supportable macro in that environment. I would hope that Atlassian is testing with these enabled since they are in the OnDemand environment and it's not responsible support to require users to all of a sudden disable something that is being provided in the instance that is often propagated throughout the entire system. OnDemand gets the benefit and pain of being alpha and beta testers...but, then, they should also be supported..

Thanks for all the references! I'll definitely watch them!

Nic Brough -Adaptavist-

No.

Atlassian release their software "when it is ready". You get hints from their blogs, and you can usually tell when something is imminent (meaning "next week" as opposed to "sometime this season"), but you won't get a formal plan.

Another good indicator is OnDemand - that goes live with a new release as soon as they believe it's supportable, which is often shortly before a full release to download. But don't rely on it, the line is still "when it is ready"

Karie Kelly1

Understand and I also manage and release software. But, you generally have targeted months and quarters for having themes available. If Versions are used - they have an expected release date so that you can use burn ups to tell how far out you are. Thus, execs know about how much time before such versions are available and can see when resources can move on to other work.

Yes, we may be one or two sprints off...but, we have to have a targeted timeline to manage investment, resources, and set customer communications appropriately. That is what I was trying to get to is a general timeline (e.g. end of 1Q, not until 2Q, etc.)

MatthewC

Karie Kelly1

Thanks for the information!

ChangJoon Lee1

I don't think this is JIRA6, but something new is coming. I guess.

http://www.atlassian.com/confluence-5-and-beyond

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira