Migration used in a sentence

Migration in a sentence as a noun

The shopping process made the migration seem easy.

Google Reader had an easy and clear migration path to export your data. I can't understand why people keep bashing Google for it.

The email doesn't give us any indication of the migration path. I don't care about your IPv6 problems or your OpenStack announcements.

I can see that we've already refunded you all the hosting fees you paid for your account, and I'll also make sure we pick up the $500 migration bill that you incurred. If there is anything else we can do please let me know.

So, the IRS can't very well execute a major migration when they don't have a budget and they aren't going to do so a few weeks before April 15th. Yes, this is wasteful, but what else could the IRS have done without approval from congress?

None of changes the fact that my original migration experience was a total disaster. I know you're experiencing growing pains.

So, this forced migration to iOS 7 is something that makes me angry, because I'm that part of the userbase than is being dragged into it kicking and screaming.

The point is to prune back the API for small devices - NOT - to make make migration of legacy code simple. For sure it would be nice if it came with a client side library to emulate OpenGL to assist in migration where people dont care about foot print size or perf.

We didnt have a good migration plan for the 1200 or so issues back then, so we kept them on Google Code. We now have about 1700 issues on the tracker Today i finally wanted to tackle the issue tracker migration, using a Python script [1] i found on Github.

I like that they have a plausible migration story for how to interoperate with existing header files. And the overall design really looks like something that would fit into all of the C and C++ work that I do without getting in the way.

If they had just said that 'Okay, your Google profile is now called Google+, and your YouTube account attached to your Google Profile is now your Google+ profile, and you can go to your settings to complete the migration', it wouldn't have been so bad. What they didn't do is offer anyone any reason to change.

I probably need to compose my thoughts into something more intelligible and write a full blog post about how I think deployment should evolve, but I have a migration to shepherd first.

It would be more accurate to analyze it as a migration, something like: college graduates are concentrating in some areas and not others, and wealth flows accordingly. Assuming, again, that systemic flows of educated people are the main causal factor in wealth changes, as Diamond claims.

Nobody, not even Torvalds or van Rossum, could throw a switch and shut down your Linux boxes or your Python interpreter, so any needed migration to an incompatible system can happen at your convenience.

Many companies choose to through money and computing resources, rather than risk a costly migration. When we have sufficiently advanced to the point where such mistakes do not depend on an individual and the automation process can take care of it, the value of the software engineer as we know the profession today will diminish greatly.

This way, the software can stand on it sown, and if it really is big of an improvement as the systemd supports suggest, the migration will happen naturally over time. If, on the other hand, using one tool continues to have the requirement of trading many other system-level tools that I already know and use, for unproven newcomers that seem to ignore the lessons of the past, well...

Everything I work on is not even considering a migration to Python 3. OpenStack? A tonne of Django applications that depend on Python 2-only libraries? A slew of automation, monitoring and system administration code that hasn't been touched since it was written? Enterprise customers who run on CentOS in highly restrictive environments? A migration to Python 3 is unfathomable.