Open mkao006 opened 8 years ago
This is an idea I've wanted to implement, but there are a few problems:
Do you have any ideas for how to allow this? I'm hesitant to just allow people to modify a library. On the other hand, adding any kind of protection is a lot of work. But maybe an override library for QA only isn't such a bad idea.
On 28 May 2016 at 22:28, Michael. C. J. Kao notifications@github.com wrote:
I think we should be able to install packages from development branch and test it on the system before releasing the new version. This will reduce the update frequency of packages and redundant versions.
For example, when I am working on the validation module, I need to constantly making changes to multiple packages as a result of review or redesigning of the module. Sometimes tit can be as small as a single line. I don't want to update the package version just due to a single line change.
I think we should be able to install from development branch, but without updating the package version.
What do you think @sebastian-c https://github.com/sebastian-c ? Any suggestions?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/SWS-Methodology/Standards/issues/11, or mute the thread https://github.com/notifications/unsubscribe/ABu_1WIfJJzpQAR99kKObG71pSSc5fPGks5qGKVqgaJpZM4IpJve .
I think we should be able to install packages from development branch and test it on the system before releasing the new version. This will reduce the update frequency of packages and redundant versions.
For example, when I am working on the validation module, I need to constantly making changes to multiple packages as a result of review or redesigning of the module. Sometimes tit can be as small as a single line. I don't want to update the package version just due to a single line change.
I think we should be able to install from development branch, but without updating the package version.
What do you think @sebastian-c ? Any suggestions?