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
Yes, I agree. I've been thinking about that. What is not clear to me yet is what would be the best structure and groups. There is no limitation on the number of groups to be used, but we might want to use no more than necessary. Did you have a structure in mind?
I agree, I would keep it simple.
I see two options :
Keeping it like this. 5 extra groups.
Or :
We could regroup DEPLOYMENT* and FIELD* under group DEPLOYMENT
And regroup PLATFORM, HARDWARE and TELECOM under HARDWARE.
That would be 2 extra groups.
We could consider a more hierarchical organisation but I think it is too early.
vturpin
added
the
1.0
For stuff that must be resolved before we are able to release 1.0
label
Sep 22, 2022
Somehow I see all those in one single logical group. There is no hardware change once a deployment is initiated. But some failures could result in a hardware swap and re-deploy. Maybe the platform might be at a higher level, but I have the impression that all the rest would be within a deployment.
justinbuck
added
1.X
For stuff to postpone and resolve only after the 1.0 release
and removed
1.0
For stuff that must be resolved before we are able to release 1.0
labels
Apr 24, 2023
Moderator: @OceanGlidersCommunity/format-maintainers
Can we expend the use of groups to
Currently, those information are stored in variable. This would be coherent with the introduction of group in the format.
The text was updated successfully, but these errors were encountered: