Here is a quite thorough review of ChangefIT v2.31 (the free version). The next release will be v2.40.
Cross-posted from http://www.support.ecofitonline.com/...ons-after-2-31.
Cross-posted from http://www.support.ecofitonline.com/...ons-after-2-31.
I just tried the free version (2.31) of changefit, it's easy to use, though, I spent quite some time experimenting, because there is no documentation which gives you a run down how to process a project from start to finish.
By using the project naming format of 0(because we don't include any portion of the date in our project#), I am not allowed to include any digits in the project name, which is very odd and inconvenient.
The promotion process needs improvement. I'd assume when we promote a project to test/qa/prod, we are quite likely to promote all tasks within the project at the same time, instead of one by one, which could be tedious if you have many objects to deploy.
The archieved source object name is cut off after the 6th character, which could make searching in the archieve a bit cumbersone, if you have similar object names >= 6 characters.
I also expect the CMS would stop one from making program changes without going throught the project process. But, using this sw still requires developers have full access to the source/object libraries, which means that the developer are not forced to use it (hence no log) in order to make a change.
I know this is a simple (and free or economic) sw, so I guess I expected too much from it.
By using the project naming format of 0(because we don't include any portion of the date in our project#), I am not allowed to include any digits in the project name, which is very odd and inconvenient.
The promotion process needs improvement. I'd assume when we promote a project to test/qa/prod, we are quite likely to promote all tasks within the project at the same time, instead of one by one, which could be tedious if you have many objects to deploy.
The archieved source object name is cut off after the 6th character, which could make searching in the archieve a bit cumbersone, if you have similar object names >= 6 characters.
I also expect the CMS would stop one from making program changes without going throught the project process. But, using this sw still requires developers have full access to the source/object libraries, which means that the developer are not forced to use it (hence no log) in order to make a change.
I know this is a simple (and free or economic) sw, so I guess I expected too much from it.
Comment