TIG-agile Sprint

GitHub address during Construction: https://github.com/helloik/tigtask Arrangement

0) Share-commit Interface)

1) Share-diff Interface)

2) Share-graph point data interface (zerrikun)

3) Share-commit info APIs)

4) work zone-submit the specified modification (LU mingkai)

5) Workspace-displays version differences of unsubmitted files (LU mingkai)

6) Submit history view-draw History overview and details (zerui Kun)

7) Submit history view-draw and submit a tree chart (zerui Kun)

8) Submit history view-displays the differences between the specified submission and the parent version (zerui Kun)

9) Test-unit test (Full Participation)

10) Test-backtracing test (Zhang kailiang, Liu haigang)

11) Test-Gui test (Zhang kailiang)

 

Burnout Diagram

 

It is not hard to see that the major progress is concentrated in the second half of agility, mainly because there was an exam in November 01, and everyone was busy reviewing, so in 10.26 ~ During this period of 11.01, some bugs were fixed and the UI interface was simply integrated. The core functions did not make much progress. After the test, all the members participated in the development, so the progress is significantly accelerated.

 

Code check-in records

For more information, see GitHub commit page.

 

Latest program running

? Submit History View

 

? Work Zone

Member experiences

? Yan zhuohui: cryptography testing is required on Thursday, and the code progress is very slow. It is a force majeure event.

? Lu mingkai: I found that there are still a lot of inskills in C ++, so I will learn more in the future.

? Liu haigang

? Zhang kailiang: after this week's agile development, my development speed and overall understanding of the project have improved a lot, and there has been a lot of communication between teams, the entire team gradually becomes United.

? Ze ruikun: although the current program is still low, the development process shows the importance and agility of team collaboration.

 

Plan for next week

1) fix known bugs

? Bugs that crash due to parent node faults (rare but reproducible)

? Bug where the diff interface of the initial node is out of bounds

2) improve and optimize existing functions and enhance stability

　　? The depth logic of the tree to be optimized requires compression depth to reduce the width occupied by the tree columns (especially when importing warehouses with hundreds of branches)

? Improve the localization of the commit interface and handle multiple situations

　　? Complete the list of recently opened warehouses

3) complete and comprehensive testing of the program to minimize the occurrence of bugs

 

TIG-agile Sprint