no release process set.
All it turns off is qa every thing is manual and this has been influenced to rest of qa peers and their juniors.
whenever you release anything to them, you will first get the latest binaries from live you have to sync with live and give back.
instead of updating .jar or .war files to production they will update individual .class file on every release.
On every release even though there is enough documentation, release notes etc will ask you to sit next to QA. compare the binaries justifying why this if condition is removed why this while loop is changed to for loop etc. which is most irritating.
if you release any major release they will at least take more then 10 months to roll out. if the development has taken 1 - 1.5 months. even though there is enough documentation and release notes.
Manual testing for the Win, they dont have any automation skill set at all.
individual developers are skillful but due to limitation of the skill set in qa, products are not going out or at least very much delayed.
If you join as qa there is no career growth, you are stuck with the lot of manual work take binaries from live, sync, sent 1 mail a day, and stay in the same skill set level, no exposure.