Parts update strategy

Parts of Pib are designed in an Onshape branch, tested then merged in main trunk. However, when this happens, extra steps should be taken.

Build tutorials and printing manuals are done manually, so this needs to be updated manually. Additionally, the print files should also be updated. Stls are updated automatically each night by a script, but Gcode repositories for Prusa printers need to be updated manually.

Each part changed should be place in this table with the date it was changed and which of the update steps have been done.

Part

Ticket associated with change

Date of merge to main - Version

Building manuals updated

Printing manuals updated

Gcode repository updated

BOM didn’t change - non printable parts are constant

Change announced on discord for community

Part

Ticket associated with change

Date of merge to main - Version

Building manuals updated

Printing manuals updated

Gcode repository updated

BOM didn’t change - non printable parts are constant

Change announced on discord for community

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

This strategy is used when fixing bugs and improving vital points in a stable release before launch or shortly after launch. However, in next versions this will be done collectively when the version is done and ready to be launched and be the next stable release.