Diff between rt2-to-rt3 v1.16 and 1.17

I were able to migrate all 50k+ tickets from RT2.0.13 to RT3.0.4 on my test
server unsing migration tool v1.16. Now I see a new version v1.17 has been
released 2 dayes later. Can someone tell me what canges have been made on the
new one. I am trying to decide if I should do another test migration using
v1.17 or v1.16 is just fine. After I did the migration, using v1.16, I could not
possibly check if all the tickets have been migrated perfectly. Hence I am
seeking any insight about the diff of these two versions

Thanks

Asif Iqbal
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x8B686E08
There’s no place like 127.0.0.1

I were able to migrate all 50k+ tickets from RT2.0.13 to RT3.0.4 on my test
server unsing migration tool v1.16. Now I see a new version v1.17 has been
released 2 dayes later. Can someone tell me what canges have been made on the
new one. I am trying to decide if I should do another test migration using
v1.17 or v1.16 is just fine. After I did the migration, using v1.16, I could not
possibly check if all the tickets have been migrated perfectly. Hence I am
seeking any insight about the diff of these two versions

With 1.17, the tickets have their encodings converted. With 1.16, certain
attachments might cause RT 3.0.4 to generate errors when trying to
display them.

http://www.bestpractical.com/rt – Trouble Ticketing. Free.