You can finish your current branches with Sage 6, thats perfectly fine. They will eventually be merged into Sage 7 but as long as there is no merge conflict you don't have to do anything.
You can of course also merge Sage 7 into your current branches, if you prefer. What is better for you depends on how long you think it'll take for the tickets to be finished and how likely a merge conflict in that part of Sage is going to be.... On Monday, December 28, 2015 at 1:24:14 PM UTC+1, John Cremona wrote: > > In the first announcement of the 7.0 series, Volker said "If you are > still working on tickets based on 6.x then you might want to use a > separate git tree for sage 7." I am wondering why -- since any > branches I have which have not yet been merged (and I have about 6 of > these) will have to be rebased onto 7.0 anyway? And that would surely > be harder if I have my old development repository with these branches > on, and a separate one with 7.0? > > John > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
