What is Flare 2016 r2?

[MC Hammer]

Is it Flare 12?
I am confused by the version number mentioned on the page that allows you to download a 30-day trial version:

This version of Flare can be installed side-by-side with most previous Flare installations, with no conflicts. This allows authors, for example, to continue working on existing projects in an earlier version while trying out new projects in the latest version of Flare.
However, Flare 2017 will install over Flare 2016 r2, rather than allowing a side-by-side installation. This applies to both activations and trial mode. Existing projects are not affected during the install, but it is highly recommended that you make a backup of all projects prior to installation.

Thanks in advance for clarifying things for me.

[RamonS]

IIRC 2016r2/2017 is what amounts to Flare 13.

[MC Hammer]

IIRC 2016r2/2017 is what amounts to Flare 13.

Thank you, but this has me confused too (I can be really thick when I put my mind to it). How can I install Flare 2017 over Flare 2016 r2 then (as per the text I quoted), if these are the same version? I assumed that Flare 2016 r2 was Flare 12 but would need confirmation. It appears, from what I read, that installing Flare 2017 will overwrite my Flare 12 installation, which is not what I want at all.

[Nita Beck]

Flare 2016 r2 is not a "dot" update of Flare 12. As Ramon said, it's what would have been called Flare 13 if MadCap had kept the numbering scheme. If you look in Windows Explorer, you'll see that its install folder actually reads "MadCap Flare 13". That's why one can have Flare 12 and Flare 2016 r2 installed on the same machine.

Flare 2017 is an update to Flare 2016 r2, so it will overwrite that version. But it's not an update to Flare 12 so won't overwrite Flare 12.

Right now, on my machine, I've got Flare 11, Flare 12, and Flare 2017 installed.

[MC Hammer]

Thank you both, I understand now. I wonder if we are not up-to-date with our Support contract (maintenance plan) with MadCap as the latest upgrade keys we received are for Flare 12.
I have never heard of Flare 2016 r2 until today, and was worried that installing Flare 2017 may overwrite the Flare 12 installation. Need to check with MadCap.
Thank you both (again).

[cayennep]

I don't know why they need to make this so confusing - I don't see the r2 reference anywhere, it seems to just be called 2017

Also, is anyone using this yet? Since it overwrites, and there's really nothing in it (including large issues many have been requesting for years, or any improvements) I'm inclined to wait.

Any feedback appreciated, esp benefits or issues. Bit disappointed in Madcap over what goes into the updates, but o well...

thanks

[Nita Beck]

Sorry this is so confusing.. I agree that it is...

Flare 2016 r2 came *between* Flare 12 and Flare 2017. It was released sometime last fall, I forget exactly when. If MadCap had continued with their longstanding numbering scheme, Flare 2016 r2 would have been called "Flare 13" (and in fact was installed into a "MadCap Flare 13" folder). Just as with all prior "major" releases, it did not overwrite prior releases.

Now along has come Flare 2017 this week. It's really just "Flare 13.x". Given its release, the download link to the latest version of Flare will be 2017, so no "r2" in sight.

So, Marie Claire's original question was, will Flare 2017 overwrite Flare 12? No. They are different releases.

But if one had already installed Flare 2016 r2, will Flare 2017 overwrite it? Yes. They are both "Flare 13". This isn't any different from a "dot" release of Flare 12 overwriting the original release of Flare 12.

The "What's New" in Flare 2017 is here: http://help.madcapsoftware.com/flare201 ... _Flare.htm.
For 2016 r2, it's here: http://webhelp.madcapsoftware.com/flare ... _Flare.htm

The release notes for Flare 2017 are here: http://kb.madcapsoftware.com/Content/Fl ... _Notes.htm.
For 2016 r2, they're here: http://kb.madcapsoftware.com/Content/Fl ... _Notes.htm

I hope this info helps.

(Personally, yes, I'm using Flare 2017. I've got a maintenance contract, so pay for my updates that way. I started immediately enjoying several new UI enhancements. Plus, I'm quite keen on the new "clean XHTML" target.)

[MC Hammer]

Thank you Nita for a very comprehensive and clear post.
I am dying to try the clean XHTML output!

[RobinS]

Like MC Hammer, while we have support in place, the last upgrade I was aware of (prior to 2017) was Flare 12.
Nothing for 2016 r2...which is puzzling! Can anyone provide the date it was released?

[RobinS]

OK, scrap that question.
It turns out that the 2016 r2 notification was sent (on 26 October 2016) to the person who pays the bill....who works in another galaxy far, far away.
Hence my ignorance!

[NorthEast]

Like MC Hammer, while we have support in place, the last upgrade I was aware of (prior to 2017) was Flare 12.
Nothing for 2016 r2...which is puzzling! Can anyone provide the date it was released?

I was only aware of 2016r2 because it was required for the MadCap Central Beta.

I didn't see anything to announce the update, but then MadCap usually email the person who buys the licence (which isn't me), not the person who registers the copy of Flare.

I mentioned this to some of the other MVPs - I found the 2016r2 release a bit strange, because it wasn't that clear when it stopped being a beta and was released.

[SKamprowski]

Just to add the answer I got from MadCap.

Version 2017 is an update or upgrade of 2016r2. While 2016r2 was installed as V13, version 2017 is V13.1

Kind regards,
Sabine Kamprowski

[Isleofgough]

The clean XHTML target does indeed create clean code. I hope they will use this to improve their ePub target to help eliminate code issues.