Hi, The first decision is to what extent we are supporting the "old" version (once the new one exists, of course). I think it would be limited to security fixes. If so, this is exactly the same as when we released 1.2, 1.3, and so on. Master is always latest (FDB, in this case) and there are branches like 1.2.x or 2.0.x if we need to backport security fixes to make a release there.
B. -- Robert Samuel Newson rnew...@apache.org On Fri, 1 Mar 2019, at 13:49, Ilya Khlopotov wrote: > There are ongoing discussions about rebasing CouchDB on top of > FoundationDB. It seems like the community is in agreement that it is > worth it to try. This would mean that we would be supporting and > extending two quite separate codebases. How are we going to do it? > > Possible options are: > - brand new repository > - separate branch which we would treat as master for FDB rebase project > > I think that separate branch approach has a number of disadvantages: > - CI might require different dependencies > - It would be awkward to open GH issues since we would have to always > refer to the project we are talking about > - There would be little friction when we open PR since the correct base > branch would need to be selected > > Best regards, > iilyak >
