Now that a new day has dawned for Brigade, it's time to change how we categorize issues and PRs.
Over the last couple years, we have applied a 2.0 label to any issue or PR having to do with Brigade 2 to differentiate it from issues and PRs having to do with 1.x.
Brigade 2 is now in the main branch and the focus of all ongoing development, so v2(.x) is should now be our de facto assumption for any issue or PR. It is now anything v1.x-related that is an outlier.
I am going to delete labels v1.0, v1.1, and v2.0. Anything v1.x-related can be tagged with a new v1 label to differentiate / specify that it's applicable to the v1 branch only. Absent this label, we can assume applicability to v2 / the main branch only.
We will continue to use milestones to assign issues and PRs to specific, upcoming v2.x releases.
I'll pin this issue and leave it open for a couple weeks for visibility.
Now that a new day has dawned for Brigade, it's time to change how we categorize issues and PRs.
Over the last couple years, we have applied a
2.0label to any issue or PR having to do with Brigade 2 to differentiate it from issues and PRs having to do with 1.x.Brigade 2 is now in the main branch and the focus of all ongoing development, so
v2(.x) is should now be our de facto assumption for any issue or PR. It is now anything v1.x-related that is an outlier.I am going to delete labels
v1.0,v1.1, andv2.0. Anything v1.x-related can be tagged with a newv1label to differentiate / specify that it's applicable to thev1branch only. Absent this label, we can assume applicability to v2 / themainbranch only.We will continue to use milestones to assign issues and PRs to specific, upcoming v2.x releases.
I'll pin this issue and leave it open for a couple weeks for visibility.