At WSO2, we don't force people to follow processes that hinder people's creativity. However, when it comes to aspects like releases & support, you have to follow the processes to the letter.
We clearly mentioned that, henceforth, you can only resolve an issue after creating a patch, attaching that to the Jira, committing to the trunk, and then applying the patch to the branch & committing it. Some of you are not following that. I think the benefit of following such a process is obvious. You may not resolve any issues until the release, unless you have attached the patch to the Jira. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
