Branching discussion aside,
I am a big +1 for relying on committers' judgement on whether an issue is
actually a bug fix, and low risk enough, that can be committed to active
branches w/o waiting for RM's approval. Right now committing bug fixes
would require that at least Stack, Lars and Andrew a
I think there can be problems with features like mvcc-seqId combo being in
a branch, because they may touch lots of places in the core that might
change frequently and cause lots of merging/rebasing overhead. So that's
another thing to consider...
On Fri, Jan 3, 2014 at 5:41 PM, Ted Yu wrote:
>
te.
>
> -- Lars
>
>
> - Original Message -
> From: Ted Yu
> To: "dev@hbase.apache.org"
> Cc:
> Sent: Friday, January 3, 2014 5:41 PM
> Subject: Re: Committing bug and test fixes to branches
>
> bq. getting large features or even moderately size
u
To: "dev@hbase.apache.org"
Cc:
Sent: Friday, January 3, 2014 5:41 PM
Subject: Re: Committing bug and test fixes to branches
bq. getting large features or even moderately sized features into branches
off of trunk
+1
We should embrace the above model.
bq. There are a handful these
bq. getting large features or even moderately sized features into branches
off of trunk
+1
We should embrace the above model.
bq. There are a handful these being worked on
I want to mention the unification of mvcc and sequence Id as one more such
feature.
Cheers
On Fri, Jan 3, 2014 at 5:32 PM
I think I like the idea of a release manger for trunk but is seems like a
potentially all-consuming task requiring superhuman vigilance.
Would working more on feature branches with invested
devs/commiters/shepards is another way of potentially achieving the goal of
a releasable trunk? This could
I think we should have a volunteer on deck as RM for the next major release
at any given time, and so this person would/should be concerned about the
state of trunk. Good idea.
As for me asking for a "soft freeze" on 0.98, I thank you for your
indulgence and it will be a thing of the past after th
We currently have 4 branches (0.94, 0.96, 0.98, and trunk).
For bug and test fixes, do we really need the release managers to agree to
every single check-in.
Andy
currently wants to stabilize the tests in 0.98 so looking at every
change there makes sense and was specifically requested by him.
W
