recording

Repository on GitHub, which provides public git repositories with URLs.

Repository on GitHub, which uses git. git can track the changes, who made them, and when they were made.

Repository on GitHub, which uses git. git is distributed.

https://github.com/kronometrix/recording/tags

https://github.com/kronometrix/recording/tags

https://github.com/kronometrix/recording/blob/master/CHANGELOG.linux.txt

https://github.com/kronometrix/recording/blob/master/CHANGELOG.linux.txt

If you have any technical problems, questions or new ideas, please contact us by opening a new change request or if you would like to join our team, https://github.com/kronometrix/recording/blob/master/docs/CONTRIBUTING.md

For any security vulnerabilities our users will open a CR immediately using https://github.com/kronometrix/recording/issues

We are conducting a review every month for all open and closed issues under github.

We are constantly checking and seeing what defects our users are reporting by closing https://github.com/kronometrix/recording/issues lot of issues.

Our change-logs ensure we keep track of all old and current fixes and open problems with our software, each for a separate platform Linux, FreeBSD, Windows, SunOS https://github.com/kronometrix/recording/blob/master/CHANGELOG.linux.txt https://github.com/kronometrix/recording/blob/master/CHANGELOG.freebsd.txt

For any security vulnerabilities our users will open a CR immediately using https://github.com/kronometrix/recording/issues

For any security vulnerabilities our users will open a CR immediately using https://github.com/kronometrix/recording/issues

For any security vulnerabilities our users will open a CR immediately using https://github.com/kronometrix/recording/issues . We are immediately responding to security incidents as found under our Issues page

We are proving all necessarily source code and tools to build the KDR project by checking: https://github.com/kronometrix/recording/blob/master/BUILD.ME. We are using in house build management system to continuously build and test KDR along with Jenkins

We are proving all necessarily source code and tools to build the KDR project by checking: https://github.com/kronometrix/recording/blob/master/BUILD.ME

All our software used in KDR is FLOSS. We are proving all necessarily source code and tools to build the KDR project by checking: https://github.com/kronometrix/recording/blob/master/BUILD.ME

Majority of all our data recorders have Perl test automated scripts which are responsible to validate and test the functionality of the data recorders.

Majority of all our data recorders have Perl test automated scripts which are responsible to validate and test the functionality of the data recorders. We are using perl (.t) scripts for this.

We are trying to test all various aspects of code branches, input fields.

We are using our in-house build, test and integration system along with Jenkins.

If we have a new functionality to be added to our project we are starting with a series of simple specs and design notes, followed by developed and a series of test scripts to ensure the original requirement is met and the software behaves correctly.

We are trying to publish all test automation scripts align with our software. We are trying to improve this part and offer 100% coverage for all our data recorders.

This is part of the developer responsibilities - when we have a new module, new recorder being developed the developer must ensure that all test cases are submitted and performed.

We can build KDR in debug mode to obtain more information if required in case of failures, stress testing, performance testing.

Any issues found during the debug mode, we are addressing separately as new issues in github.

We are trying to reduce all warnings coming from different modules or libraries used by KDR.

The founder and original developer is dedicated as well for all security aspects of Kronometrix Data Recording software. He is constantly checking forums and mailing lists posting vulnerabilities and critical issues found in software. He is the main designer as well for all secure aspects of KDR.

The founder and original developer is dedicated as well for all security aspects of Kronometrix Data Recording software.

We are using HTTPS and SSH + SCP protocols for this.

We are using HTTPS

We are trying to issue an immediate security update if we found issues with KDR or with some other 3rd party library used by KDR

We are trying to issue an immediate critical updates if we found issues with KDR or with some other 3rd party library used by KDR. In general KDR is used in many production systems and we are required by our customers to act immediately.

We are not storing private or confidential information under any public or private repositories.

We are continuously using Perl::Critic for Kronometrix Data Recording (KDR) software.

We are continuously using Perl::Critic for Kronometrix Data Recording (KDR) software.

We are addressing immediately problems found by Perl::Critic and if we are not able to fix them we re-design or include those for a maintenance release.

We are using Perl::Critic for all our data recorders as soon as we are changing code. We are trying to rely on its output to write better software.

We are continuously using Perl::Critic for Kronometrix Data Recording (KDR) software.

We are continuously using Perl::Critic along with Devel::NYTPROF to ensure our software is bug free and does not create memory leaks or have security vulnerabilities.

We are trying to use as much as possible Test::Assertions for all runtime assertions.

Anything we found based on results from Test::Assertions, Devel::NYTProf, Devel::Coverage we are opening as new issues and we address them in a proper manner.