> It has a different connotation of the quality of what's in the branch. However, I think we can go ahead with filtering without blocking on
adding this.
Discussed this with Tim yesterday. We considered making "Inactive" an independent flag, so there would be a clear distinction between Mature+Inactive and e.g. Experimental+Inactive. Since I am also contemplating making "Merged" a separate flag (useful when we will have automatic status updating and landing-target), I think we should postpone adding more lifecycle-status until we have a clear view on how we want to evolve branch status in the next months.
> It has a different connotation of the quality of what's in the branch. However, I think we can go ahead with filtering without blocking on
adding this.
Discussed this with Tim yesterday. We considered making "Inactive" an independent flag, so there would be a clear distinction between Mature+Inactive and e.g. Experimental+ Inactive. Since I am also contemplating making "Merged" a separate flag (useful when we will have automatic status updating and landing-target), I think we should postpone adding more lifecycle-status until we have a clear view on how we want to evolve branch status in the next months.