Following 4 branches have been created and are now available for commits targeted for 4.8.0 only.
4.8-HBase-0.98 (from 4.x-HBase-0.98) 4.8-HBase-1.0 (from 4.x-HBase-1.0) 4.8-HBase-1.1 (from 4.x-HBase-1.1) 4.8-HBase-1.2 (from master) Any commit targeted for 4.8.1 or 4.9+ along with 4.8.0 can go in master and 4.x branches now. Regards, Ankit Singhal On Thu, Jul 28, 2016 at 4:25 PM, Ankit Singhal <ankitsingha...@gmail.com> wrote: > Ok, Given that 4.8.0 RC is taking time , we can fork 4.8-HBase-x.y > branches so that new features and bugs target for future releases(4.9+) can > be committed in 4.x branches and master. > > Whatever is targeted for 4.8.0 needs to be committed in all 8 > branches(three 4.x branches , master, four 4.8-HBase-x.y) as all 4.8 > releases(including 4.8.0 or 4.8.x) will be done from 4.8-HBase-x.y branches. > > I'll create the following new branches tomorrow morning IST, > 4.8-HBase-0.98 (from 4.x-HBase-0.98) > 4.8-HBase-1.0 (from 4.x-HBase-1.0) > 4.8-HBase-1.1 (from 4.x-HBase-1.1) > 4.8-HBase-1.2 (from master) > > Let's discuss if someone has any concerns. > > Regards, > Ankit Singhal > > On Sun, Jul 24, 2016 at 2:19 PM, <la...@apache.org> wrote: > >> Also, can we branch 4.8-x in git?That way bigger changes can still go >> into the 4.x branches, while bugs are fixed in 4.8-x branches. >> -- Lars >> >> From: James Taylor <jamestay...@apache.org> >> To: "dev@phoenix.apache.org" <dev@phoenix.apache.org> >> Sent: Thursday, July 21, 2016 7:16 PM >> Subject: new 4.8.0 RC? >> >> How about a cutting a new RC now that the licensing work is complete, >> Ankit? Looks like we can simplify the voting too by just having a single >> vote across all versions by just include all the information in one VOTE >> thread. >> >> Would be good to get PHOENIX-3078 in too, if possible. We've had a few >> other fixes come in which IMHO are all ok to include in the new RC. >> >> Thanks, >> James >> >> >> >> > >
