At what point in a project is it considered beyond the "bootstrap" phase? The way I see it, Bootstrap is the perfect CSS template to use when starting a project. But at some point the project will reach a level of maturity and complexity where "upgrading" to a new version of Bootstrap is perhaps far more effort (and error-prone) than it's worth. This is especially true when they do things like renaming classes or reorganizing the layout structure.

Note I think this applies primarily to the CSS part of Bootstrap which I consider to be more of a template than a library or framework; the JavaScript plugins are always pretty painless to upgrade.

Definitely agree. My company has been switching over to a centralized version of Bootstrap for our internal applications (over 300 in total, maybe 40 use Bootstrap so far). I oversee the upgrade process, and quickly/easily doing so remains a hurtle I have yet to gracefully overcome.

The best solution I've been able to cook up is adapting their changelog into a step-by step tutorial for developers to use when upgrading, though I'd love to hear any suggestions on improving that process!

I've heard this before and I think it's a great topic. Is the addressable issue that there needs to be a way to "upgrade" to the newest version or is there a fundamental oversight into how we handle upgrades of amazing resources like this. I feel like there is an elegant solution out there but it just hasn't been adopted into CSS and JS yet.

We haven't announced it yet, but we're working on this as part of what we're doing at BootstrapHero - http://www.bootstraphero.com

We were targeting to have it out more for 2.x to 3.0 as that will be a bigger jump.

I think by posting that, you did just announce it... ;) But yeah, that's awesome! Can't wait to see it!

They have reasonable detail in their changelog -> https://github.com/twitter/bootstrap/blob/master/CHANGELOG.m...

The old docs are tagged in github if you wanted to diff them.