I guess my point was that we do need to test the branch but rather only the
tag. So the only important part is to ensure consistency between CHANGES.txt
and the tag (and jira, but that can be changed after the fact too).Then I do
all testing based on the tag. If I find any issues I start again (i.e. make the
necessary changes and update CHANGES.txt and/or move the tag).
So as long as there are no issues found during the final testing, which is
usually the case at least in 0.94, there is never any issue with other commits.
-- Lars
From: Andrew Purtell <apurt...@apache.org>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Cc: lars hofhansl <la...@apache.org>
Sent: Monday, January 26, 2015 10:32 AM
Subject: Re: No commits to branch-1.0 today please
.. and because we are using git, this is all local. I won't be able to commit
to the branch if someone has changed upstream, so when that happens I fetch,
rebase, redo the tag, then push. Upstream doesn't get messy.
On Mon, Jan 26, 2015 at 10:26 AM, Andrew Purtell <apurt...@apache.org> wrote:
I update the version in the POMs, update CHANGES.txt, then tag, then do the
rest of the release mechanics, so the time where commits to the branch would be
a problem is very short, < 5 minutes.
On Sun, Jan 25, 2015 at 11:00 PM, Enis Söztutar <enis....@gmail.com> wrote:
Do you have a script to update CHANGES.txt ? We should bring that in to
make_rc.sh.
Usually for me, it is mostly running update CHANGES.txt, run make_rc.sh,
then tag.
Enis
On Sun, Jan 25, 2015 at 8:36 PM, lars hofhansl <la...@apache.org> wrote:
> The way I avoid this for 0.94 now is to create a jenkins job specifically
> for the RC tag and use that to build/test.
> That way I only have avoid commits between the time I create the updated
> CHANGES.txt and when I push the tag (usually 1 or 2 minutes).
> As soon as the tag is created new commit do not harm, as the tests are off
> the tag.
>
> -- Lars
>
> From: Enis Söztutar <enis....@gmail.com>
> To: "dev@hbase.apache.org" <dev@hbase.apache.org>
> Sent: Sunday, January 25, 2015 5:41 PM
> Subject: Re: No commits to branch-1.0 today please
>
> No worries. Saw that issue but did not have the time to run the tests.
>
> Enis
>
>
>
> On Sun, Jan 25, 2015 at 5:38 PM, Andrew Purtell <apurt...@apache.org>
> wrote:
>
> > Crap, sorry, I did one. It's a new case in TestShell. I didn't see this
> in
> > time, sorry. No more from hence from me.
> >
> > On Sun, Jan 25, 2015 at 5:21 PM, Enis Söztutar <e...@apache.org> wrote:
> >
> > > I am trying to cut the 1.0.0RC1. Appreciate if no commits come in for
> > > today.
> > >
> > > Enis
> > >
> >
