Ok, I give up. I will refrain from committing here.
On Wed, Jul 8, 2015 at 10:26 AM, James Taylor <[email protected]> wrote: > The pom(s) for master should be 4.5.0-SNAPSHOT, but it looks like that's > what they are (at least in my local version of master). > > Thanks, > James > > On Wed, Jul 8, 2015 at 10:18 AM, Andrew Purtell <[email protected]> > wrote: > > > Pardon for bringing up again something I suspect others have already > > struggled with. > > > > The POMs in master branch carry the version 5.0.0-SNAPSHOT. The POMs > > in 4.x-HBase-0.98 branch carry the version 4.5.0-HBase-0.98-SNAPSHOT The > > POMs in the 4.x-HBase-1.1 branch that was apparently dropped also carried > > the version 4.5.0-HBase-1.1-SNAPSHOT. > > > > Where is the 4.5.0.... version for HBase 1.1 and up? I guess this will be > > branched from master at some point? Will it be cool to renumber master > back > > down to 4.5.0.... when branching from master for HBase 1.1 and up? > > > > I pushed an empty ref for '4.x-HBase-1.1' so that should be dropped again > > now. > > > > > > > > > > On Wed, Jul 8, 2015 at 10:05 AM, Andrew Purtell <[email protected]> > > wrote: > > > > > I committed one patch and it ended up being a commit storm because at > > some > > > point a branch named "4.x-HBase-1.1" went away. I had it as a local > > > tracking branch. > > > > > > So where do commits for 4.x on HBase 1.1 and up go? Totally confusing > > > branch situation. > > > > > > -- > > > Best regards, > > > > > > - Andy > > > > > > Problems worthy of attack prove their worth by hitting back. - Piet > Hein > > > (via Tom White) > > > > > > > > > > > -- > > Best regards, > > > > - Andy > > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > > (via Tom White) > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
