Making the decision about whether to do it and in which release can be
kept as 2 separate decisions.
The discussion about benefits, skill sets, technical implications is one
issue.
How will the decision be made (criteria, etc.)?
Who will investigate? What tests need to be done to prove the
viability. What document will record the conversations and analysis?
When will it be done? How it should be integrated into the release
roadmap and development structure? Who will redo and test the scripts?
Who will redo the documentation?
These are all separate issues that only become important after the
decision is made to actually do it.
Ron
On 20/08/2014 10:34 AM, Pierre Smits wrote:
Jacopo,
What scripts do you have in mind that need to be enhanced or added? Can you
outline your thoughts for each?
Replacing current ant scripts or even encasing these in another convention
means that users (both system administrators and developers) need to update
their knowledge and skills. Plus all related documents need to reviewed as
well. This all takes time. And should therefore be planned.
We have keep in mind that the majority of our user base is not a group of
developers but businesses. And these businesses have ease of operations and
trustworthiness in mind. Not ease of development.
Nevertheless, if we are to go on this path I suggest that we do this isn a
separate development branch. That eventually can be brought back to a
release.
Regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Wed, Aug 20, 2014 at 2:51 PM, Jacopo Cappellato <
jacopo.cappell...@hotwaxmedia.com> wrote:
http://www.gradle.org
What do you think?
We could write more powerful and elegant build scripts, add also have a
dependency management system. It is licensed under ASL2.0.
Jacopo
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
