You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OK for one branch, but we can make different branches locally to play with the routing tool;
personally I know how to use it but I'm not an expert (saturday afternoon is a good moment to route some tracks, but first we have to place the components and to define the mechanical dimensions, the rest is usual business xD).
@2010019970909 I created this ticket out of the meeting minutes, but anyway we agreed to start this all together, we might have to agree on discord when to have this meeting. if no suggestion comes up, it might end up being next Sunday 19h during the Team meeting. @Informaticore or should we plan it separately ?
From what I understood, the routing is not that of a big deal that requires automatic routing, but maybe some routing assistance features might make the manual routing smarter and faster.
For branching, as long as it's local, it of course does not matter, only one routing branch will be merged back so to say which will be the commonly used one.
Also we might have to coordinate the routing with regards to the review cleanup, on what should come first. Given that any cleanup in the schematics result in reworking the routing as well, it might be that we shift routing till the "clean freeze" of the schematics :)
notes from @Informaticore Team meeting minutes :
How are we doing the routing?
The text was updated successfully, but these errors were encountered: