I'll start by clarifying, I work for an outsourcing company.
On my current project, we have release cycles. There's a requirements phase, a development phase and a stabilization phase.
We have a code freeze at the end of the dev phase, before stabilization, after which no new functionality should be worked on. Requirements, gathering, for the next cycle, should happen at the same time as stabilization, though it's normally continuous. Dev is self explanatory and stabilization is for bug fixing.
After stabilization we release the completed functionality to the client. They're supposed to do additional testing, normally don't, and a few other thing to prep for deploy to prod and that can sometimes take our whole cycle.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'll start by clarifying, I work for an outsourcing company.
On my current project, we have release cycles. There's a requirements phase, a development phase and a stabilization phase.
We have a code freeze at the end of the dev phase, before stabilization, after which no new functionality should be worked on. Requirements, gathering, for the next cycle, should happen at the same time as stabilization, though it's normally continuous. Dev is self explanatory and stabilization is for bug fixing.
After stabilization we release the completed functionality to the client. They're supposed to do additional testing, normally don't, and a few other thing to prep for deploy to prod and that can sometimes take our whole cycle.