This was first posted on Sourceforge on 27/11/2012
We are now in a position where we have some stable code that could be released. Most of the known bugs in webERP have been fixed in our code. Should we release a version now?
What are the arguments against?
If we release now there will be little differentiation between us and webERP.
Our infrastructure is not yet ready, no web site, wiki, forum, bug tracker etc. So far we haven't raised the money for a domain name.
What are the arguments for?
A release will start to get us noticed, hopefully generating more developers, and more help.
It will get some momentum in the project.
Users will be able to take advantage of the bug fixes we have already done.
Munir Patel
We are now in a position where we have some stable code that could be released. Most of the known bugs in webERP have been fixed in our code. Should we release a version now?
What are the arguments against?
If we release now there will be little differentiation between us and webERP.
Our infrastructure is not yet ready, no web site, wiki, forum, bug tracker etc. So far we haven't raised the money for a domain name.
What are the arguments for?
A release will start to get us noticed, hopefully generating more developers, and more help.
It will get some momentum in the project.
Users will be able to take advantage of the bug fixes we have already done.
Munir Patel
No comments:
Post a Comment