Viewer 2.5.213.0 and 2.5.213.1 version information

[Spiff]

Dear Tracker Support,

The Editor is now the main focus of development for viewing and editing and the Viewer will no longer be actively developed.
However, recently, the Viewer had an update to build 2.5.213.0 (27[?] October 2013) and subsequently to build 2.5.213.1 (14 November 2013).
As this may have been two of the last updates for the Viewer, it would be good to know what was fixed with those updates.
However, on the Version History page for the Viewer the most recent information is still that for the 2.5.212.0 release (29 August).
I'm not complaining, I'm just noticing.
Can you tell me, please, when will the version information for 2.5.213.0 and 2.5.213.1 be available on the Version History page?

Thank you very much
and best regards,

Spiff

[Will - Tracker Supp]

Hi Spiff,

Thanks for the post - I've just checked the Version History for the Viewer, and can confirm that. I'm not sure that we're updating the change log for the Viewer any more, but I will have to ask the Dev. Team to confirm that.

As for the updates - generally speaking, we're not actively developing the Viewer, but if something is found that we feel should be fixed, then we will still fix the issue and release a new build. I can't confirm or deny that we will continue doing this forever, or for how long if there is a 'sunset' period, but for now this is the case.

Cheers,

[Spiff]

Hi Will,

Thank you very much for your reply.
You wrote,

I've just checked the Version History for the Viewer, and can confirm that.
I'm not sure that we're updating the change log for the Viewer any more, but I will have to ask the Dev. Team to confirm that.

Thanks very much.
I really hope the Version History page for the Viewer will be continued to be updated as long as new builds will be released to fix something, sporadicly.
I think that if something is fixed, sporadicly, it is best that those changes are shown in the change log, as usual.


Thank you very much
and best regards,

Spiff

[Will - Tracker Supp]

Hi Spiff,

Having spoken to colleagues on this, they've told me that Version history should continue to be updated, which obviously makes sense.

I will put in a word with the Developers to ensure that the Version History is updated to reflect the latest changes.

Cheers,

[Spiff]

Ah, great.
Thank you very much, Will.

Best regards,
Spiff

[Will - Tracker Supp]

Not a problem, always glad to help

[Spiff]

Having spoken to colleagues on this, they've told me that Version history should continue to be updated, which obviously makes sense.
I will put in a word with the Developers to ensure that the Version History is updated to reflect the latest changes.

Tomorrow, it is two weeks since then.
The Viewer's Version History page still shows the information for the 2.5.212.0 release (29 August) as the most recent information.
Build 2.5.213.0 (27[?] October 2013) and build 2.5.213.1 (14 November 2013) are still not mentioned on the viewer's version history page.

Again, I'm not complaining, I'm just noticing, and I know the developers team is very busy with the Editor, but I think it would be good if the version history page for the Viewer can soon be updated.
Thank you very much.


Best regards,
Spiff

[Stefan - PDF-XChange]

Hi Spiff,

Build 213 was mostly fixing some bugs, and 213.1 was fixing errors in the installation packages so no changes to the actual product happened between 213.0 and 213.1. Besides the huge workload we've also had some developers sick - so this has strained us even more, but we will try to get that history page up to date as soon as possible.

Regards,
Stefan

[Spiff]

we will try to get that history page up to date as soon as possible.

Thank you very much, Stefan.

Best regards,
Spiff

[Stefan - PDF-XChange]

[lmacri]

Bump. Any update on when the change log for PDF-XChange Viewer 2.5.213.x will be posted at https://www.pdf-xchange.com/PDFXV_history.html? It's been almost 2 months since build 213.0 was released.

[Spiff]

Hi lmacri,

Yes, it's almost two months since Viewer build 2.5.213.0 was issued,
almost six weeks since 2.5.213.1,
four weeks since I first asked about updating the Viewer's Version History page,
and two weeks since I asked again,
bus as today it is the day of Christmas Eve, I didn't want to ask again.
I suppose it'll be after New Year until the Viewer's Version History page will be updated.

Best regards
and happy holidays,

Spiff

[Walter-Tracker Supp]

Thanks for your patience (and for the reminders!)

-Walter

Hi lmacri,

Yes, it's almost two months since Viewer build 2.5.213.0 was issued,
almost six weeks since 2.5.213.1,
four weeks since I first asked about updating the Viewer's Version History page,
and two weeks since I asked again,
bus as today it is the day of Christmas Eve, I didn't want to ask again.
I suppose it'll be after New Year until the Viewer's Version History page will be updated.

Best regards
and happy holidays,

Spiff

[Spiff]

Yesterday, PDF-XChange Viewer was updated to build 2.5.214, so I noticed.
Well, that's another one pending for the version history page.
But that's for later, of course.
Happy New Year's Eve, everyone.

[Paul - PDF-XChange]

HI Spiff,

happy new year to you also - I heard rumblings from deep underground that this is going to be done in the next few days...

Lets see if the first week of the new year brings updated Versions Histories. If not - you know where to catch us...

regards

[Spiff]

Nice to see there was another Viewer update, build 2.5.214.1, 8 January 2014,
good to see the Viewer is still maintained with updates, when essential updates are required.
But it's another one pending for the version history page, of course.
Now it's builds 2.5.213.0, 2.5.213.1, 2.5.214.0 and 2.5.214.1 waiting for the version information details.
Will this week bring an updated version history page for the Viewer?
Lets see.

Kindest regards,
Spiff

[Paul - PDF-XChange]

Hi Spiff,

Will this week bring an updated version history page for the Viewer?

Yes.

[avada]

This is ridiculous. How hard it is to write a couple lines immediately when you update the program? Everyone else can do it....

[Paul - PDF-XChange]

Hi avada,

it's not a question of how difficult it is but practicality and priority. Those that know the details of the changes have other more pressing tasks at hand. It has been promised for this week and I'm confident it will be done.

hth

[Spiff]

Yay!
I notice that the Viewer's version history page has been updated, as promised!
Thank you very much.

Two issues, however:

1.
Builds 2.5.213.0, 2.5.214.0 and 2.5.214.1 are now documented, but not the 14 November 2013 2.5.213.1 update.
It would be really appreciated if also the update details for build 2.5.213.1 would be specified.

2.
For build 2.5.214.1, release 8 January 2014, there is now specified:
Resolved critical issue with loading AcroForms introduced in the previous build. [Critical error or bug fix] [PDF Engine]
A critical fix in what sense?
The meaning of "critical issue" or "critical bug fix" is not clear.
Was it a fix for a security vulnerability, perhaps? Or just a non-security issue?

Such information is why I think it is important that the version history page is well maintained.
And in case of critical bug fixes, I think it is important that the specified details are clear regarding the kind of critical bug fixes. What kind of critical bug fixes are meant, security fixes or other kind of critical fixes?


Thank you very much
and best regards,

Spiff

[Will - Tracker Supp]

Hi Spiff,

Thanks for post - for build 213.1., only the build number was updated for consistency between products, so there were not any actual bug fixes or feature implementations.

A critical fix or critical issue is simply defined as an issue with something that is considered critical to the headline functionality of the product. In this case, it was an issue with forms no longer being properly recognized and so could not be filled out with the Viewer. We considered this critical to the Viewer functionality and in desparate need of fixing.

Cheers,

[Spiff]

Thank you very much for your clear reply, Will.

I never would have expected that with the update to build 2.5.213.1 only the build number was updated, with no other changes or fixes than just that build number update.

And regarding to "critical issues" or "critical bug fixes", you explained about the fix in build 2.5.214.1, which was not a fix for any security vulnerability. But now I still wonder, if there's ever a security vulnerability fixed in the Viewer or the Editor or one of the other Tracker Software products, how will that be reported in the version history? Similar to the January 2013 security fix, I guess, with a clear remark regarding security and a reference to and an entry on the Tracker Software News, Press & Events page.
Ah, I think I answered my own question.


Best regards,
Spiff

[Will - Tracker Supp]

Hi Spiff,

Not a problem

And regarding to "critical issues" or "critical bug fixes"...

That's correct, all security fixes//issues should be clearly outlined as such.

Cheers,