If you are using Sitecore 8.1 then plan for 8.2 , Here are the key points.

I will describe the key decision points, some key points for the migration and key challenges.

Key decision points.

If you have been using checkboxes in the template then may face some random behaviour.

This was a random behaviour in this version (8.1 U2) where checkbox value got automatically unchecked.

I have noticed this issue and discussed with the support team, this has been identified as an issue and fixed in 8.2(Initial release).

If you have some business logic based on checkbox then it may effect.

If you have used bucktable structure. will affect, sometime your content may come out from the bucktable structure, As the of bucktable items may reset randomly

Release note:-https://dev.sitecore.net/Downloads/Sitecore_Experience_Platform.aspx

There is a lot of improvement in the latest version, mostly in performance, experience editor, content editor and fixes.

Improvement details:-

1. Enhanced Experience Editor features like

• You can track the associated content in the experience editor.
• Workflow status can be checked for individual components.
• Performance improvement to load the page
• Improved security and search
• Content Foundation improvements (Dependency Injection, Caching and Performance)
• Support for Express Migration (installed separately)
• Enhanced Path Analyzer component

You will find more option in the admin panel, like Dependency injection configuration, Logs and support packages.

Support configuration can be directly uploaded to Sitecore through FTP.

Process for the migration

If you are upgrading from Sitecore 8.1 rev. 151003 (Initial Release) or later, you can upgrade directly to Sitecore 8.2 rev. 161115 (Update-1). However, if your solution is based on an earlier version of Sitecore, you must first upgrade to Sitecore 8.1 rev. 151003 (Initial Release). 

Challenges and fun.

Fist challenge, If you have used a custom configuration then make sure the syntax should be the same, even the description section.

Sitecore 8.2 matches the exact signature, earlier when we were adding any configuration it was creating altogether a new entry.

Example, Schedule publishing -

If you let's say change the description section, then it will not work and render two entries for the particular item.

Second, if you have used any custom popup for a Bispok application or used any MVC controller for the CRUD operation, you may not be able to access this.

As Sitecore 8.2 version introduced new pipelines and this can be found in Sitecore.MVC.config file

<processor type="Sitecore.Mvc.Pipelines.Request.RequestBegin.EnsureLoggedInForPreview, Sitecore.Mvc"/>

Bispok application or custom controller. resolve this item, either the request should use the proper shell or have to customize the pipeline. else you will not be able to access the else you will not be able to access the to

If you have any issue, then feel free to ask here or connect through Sitecore Community

https://kb.sitecore.net/

Would be happy to help.