fix outdated document - developments.md

[youngtaekiim]

No description provided.

[basheerFZ]

@youngtaekiim / @leeeunkoo --> we would like to know why you have removed the changes that were delivered by LGSI which was already merged, Is this by mistake the changes are Overwritten Or you wanted to move the changes to some other location.

I believe all our work related to documentation of unit testing, codecovarage, static analysis, integrattion testing has been removed

[youngtaekiim]

@youngtaekiim / @leeeunkoo --> we would like to know why you have removed the changes that were delivered by LGSI which was already merged, Is this by mistake the changes are Overwritten Or you wanted to move the changes to some other location.

I believe all our work related to documentation of unit testing, codecovarage, static analysis, integrattion testing has been removed

A few days ago, I did all steps in our documents. (development.md getting-started.md , etc...) And I fixed old (not operated) version.

During the testing, I found that development.md include very general (usual) informations about rust, not piccolo. Almost of all works of LGSI is still alive. Only unit test and cargo tarpulin informations are partially removed.

For example, mamy parts of unit test contain official rust docs information. This is not the scope of piccolo.

Please let me know if you have other opinion. I will always listen.

[basheerFZ]

@youngtaekim,

First why do we still call this development as piccolo, we are of the opinion that we are working on Pullpiri and not Piccolo.

I agree with you that it is same as rust docs information, but how will the developers know what tools has been configured and used in our project for eg usage of tarpaulin for code coverage and what is the codecoverage policy set for our project, but its not mandatory that we need to use tarpaulin we can use any other tool also, so how will we convey this information, We believe these are all part of the development process.
note:-

Also how abt the developers updation of license information of their modules, security vulnerabilities check if their modules are run for vulnerabilities ?

Lets discuss these items are required or not needed as part of our conference call and conclude the same.