workflow - Continuous integration and large architectural changes. How to handle them? -
i reading this answer in trying understand how work multiple developers working on multiple branches of project. first reflex want jenkins run separate build each branch, understand it, bad way approach problem.
now, see how having small features or parts of features merged main branch preferred way go, can't quite wrap head around happens when project goes through large architectural change.
say have web project written in angularjs , team decides future of project, needs moved on using reactjs instead. said current project have reasonable number of features implemented , tested. @ point, can't imagine smaller increment new "feature" of using reactjs other having on part current state of project, meaning every test passing should still pass once it's done. else mean regression project , know of few clients ok this.however, that's hardly going case until switch 100% done, not small amount of work.
i might not understand concept perfectly, don't see feature toggles working here (especially if move reactjs requires modify, say, gruntfile since inevitably break things lot). team doing migration needs tell rest of team not touch project until it's ok? seems weird solution me.
so i'll admit, i'm @ loss proper workflow here. input appreciated our development process try , make better, limited experience in field.
Comments
Post a Comment