massalabs / station-massa-node-manager

MIT License
0 stars 0 forks source link

upgrade from thyra to massaStation #60

Closed B-Naoufal closed 1 year ago

B-Naoufal commented 1 year ago
$\textcolor{Darkorange}{\textsf{DoR}}$ Tasks can’t be started if the following info doesn’t exist. * If the task is an investigation, make sure a specific time-box is associated and clearly stated in the task * Task must be estimated (in dedicated field) * Define the action plan you'll follow to achieve this task. Add it in comment * An action plan is: * An ordered list of tasks * with an owner on each task * an ETA * if blockers or dependencies are identified, they must be clearly listed and a solution should be found before starting the issue. * For front-end tasks, designs must be linked, accessible by all and MR must contain [context], [before/after image][reproduction instructions] If one of this point or info is missing, please raise the point ASAP to the PM.

Context

Describe / explain why we should do this: motivations, context or other info. Keep it brief and simple

User flow

Describe the user flow using user stories so the end result is super clear

How to

List the step-by-step to get it do if needed

Technical details

Give the technical insights so anyone in the team can tackle the tasks

QA testing

Does this task require some QA tests ? If yes, explain how to validate it

$\textcolor{Red}{\textsf{DoD}}$ Before putting this ticket in code review, tick all the boxes bellow. More details [here] (https://www.notion.so/massa-innoteam/Plan-for-the-mainnet-c574da44a4854eb3841a5f2e93a2977c?pvs=4#e7db6fa53fa84264954075011432ce70) & [here] (https://www.notion.so/massa-innoteam/Industrialization-of-Frontend-0f7425f14cd3490a949f31978916ee41?pvs=4) if needed - [ ] Pull request is small (break it down as much as you can) and approved by 2 reviewers - [ ] You are proud of what will / has been merged - [ ] Code and functionality implemented is working on all OS - Windows 10 + - Linux Ubuntu - MacOS catalina + - [ ] Endpoints are covered by units tests and are monitored (ie: we are notified -somehow- when something is down) - [ ] Where relevant, implemented screens are pixel perfect with the designs for the following screen sizes - 1920 x 1080 px - 1440 x 900 px - 1366 x 768 px - [ ] Where relevant, all info must appear in less than 1 sec on the front-end - [ ] Functionalities are fully working (errors messages exist, all use cases are covered - when applicable) - [ ] Related documentation has been updated if needed - [ ] Functionality are QA reviewed on every OS