I've renamed the branches in git at this point as described in this thread. Really nice that the dev branches are on top of all the JIRA named branches.
On Thu, Jan 2, 2020 at 7:28 AM Stephen Mallette <[email protected]> wrote: > While we've stuck to the pattern of naming our release branches as > "tp<version>" as in: > > tp33 = 3.3.x > > I think we should consider renaming to something more recognizable - > perhaps: > > 3.3-dev = 3.3.x > > which I think does two things: > > 1. pushes the the development branches to the top of the dropdown in > github above all the JIRA feature branches > 2. hopefully allows new contributors to realize that we have other lines > of development (more so than we do now at any rate) > > The main impact that I can think of is that all existing PRs would need to > be retargetted. That's mostly a concern for older PRs that have been > hanging around forever (which should probably be closed anyway). I think > that if we go this route I'll either close, re-target or if a third-party > PR that's gone orphan but still has value I'll pull it to a branch of our > own and hold it there. Is there other impact to consider? > > Assuming no objections or worries I'm not considering right now, I'll > proceed with this change next week. > > >
