RHQ Release - master Branch Open
Lukas Krejci
lkrejci at redhat.com
Tue Feb 28 15:44:17 UTC 2012
+1000
The only thing that prevented me from committing to master during the freeze
was that I wasn't satisfied with my code. I would have never remembered
to not commit - and I read the email.
People make mistakes. Branching prior to release prevents most of the problems
and is just too easy to not do it, imho.
----- Original Message -----
> From: "Simeon Pinder" <spinder at redhat.com>
> To: rhq-devel at lists.fedorahosted.org
> Sent: Tuesday, February 28, 2012 4:29:09 PM
> Subject: Re: RHQ Release - master Branch Open
>
>
>
> ----- Original Message -----
> > From: "Stefan Negrea" <snegrea at redhat.com>
> > To: rhq-devel at lists.fedorahosted.org
> > Sent: Tuesday, February 28, 2012 9:46:40 AM
> > Subject: Re: RHQ Release - master Branch Open
> >
> > Hello Simeon,
> >
> > I actually did this on purpose yesterday. Primarily because I think
> > we need to have a release process that is hands-off. My idea is to
> A worthy goal but as your experience here would support there is
> always at least one problem somewhere and some iteration that is
> necessary. A branch gives you the isolation necessary to do or not
> do release iterations if need be and the other N developers on the
> team are not impacted. Hands off or not we should take steps to
> anticipate the unexpected environment(hudson/brew) or code hiccups
> that do occur. Think of it as insurance.
>
> > run the release script and let it take care of everything. Having
> > confidence in the stability of code based on existing builds, I
> > knew
> > that master will not be locked for more than just a few hours.
> > Overall, I think this was a success because the branch was blocked
> > for under 5 hours; and it could have been even half of that time if
> > I did not have to fix a small issue in the release script.
> Why not just build the branching into the release script early on?
> I'm not a fan of code freezes if we don't need them because you
> can't be sure that everyone got the messages and then inevitably you
> have a developer or two who is asking are we still in code freeze.
> Throw in some timezone differences and it gets trickier. Since
> we're in git and branching is so cheap I think we should just do the
> branching early on. Minimizing code freezes supports the 'commit
> early and often practice'. Automated or not it's a cheap way to
> keep the code flowing and the release isolated from unintentional
> commits. Win win imo.
>
> >
> > I totally agree with your strategy (branching manually ahead of
> > time
> > to have the original branch open for commits) but only if the
> > release process would block the original branch for a longer period
> > of time.
> >
> >
> > Thank you,
> > Stefan Negrea
> >
> > ----- Original Message -----
> > > From: "Simeon Pinder" <spinder at redhat.com>
> > > To: rhq-devel at lists.fedorahosted.org
> > > Sent: Monday, February 27, 2012 2:25:18 PM
> > > Subject: Re: RHQ Release - master Branch Open
> > >
> > > Hi Stefan or others doing community builds in the future,
> > >
> > > As an enhancement to the process the next time around, if you
> > > create the release branch before starting the release build
> > > process then there is no need to freeze the master branch. The
> > > isolation needed for the automated scripts and release process
> > > is
> > > achieved by creating the release branch up front and using
> > > 'tag'
> > > as the scm strategy.
> > >
> > > -Simeon
> > >
> > > ----- Original Message -----
> > > > From: "Stefan Negrea" <snegrea at redhat.com>
> > > > To: rhq-devel at lists.fedorahosted.org
> > > > Sent: Monday, February 27, 2012 2:30:18 PM
> > > > Subject: RHQ Release - master Branch Open
> > > >
> > > >
> > > > The release branch and tag have been successfully created.
> > > > Master
> > > > branch is open for commits.
> > > >
> > > >
> > > > Thank you,
> > > > Stefan Negrea
> > > >
> > > > ----- Original Message -----
> > > > > From: "Stefan Negrea" <snegrea at redhat.com>
> > > > > To: "rhq-devel" <rhq-devel at lists.fedorahosted.org>
> > > > > Sent: Monday, February 27, 2012 8:51:01 AM
> > > > > Subject: RHQ Release
> > > > >
> > > > > Hello Everybody,
> > > > >
> > > > >
> > > > > I will start the process to cut a new RHQ release. It should
> > > > > take
> > > > > about 2 hours. Please refrain from committing any code into
> > > > > the
> > > > > master branch during this time. I will send an email out as
> > > > > soon
> > > > > as
> > > > > the process finishes.
> > > > >
> > > > >
> > > > >
> > > > > Thank you,
> > > > > Stefan Negrea
> > > > >
> > > > > Software Engineer
> > > > >
> > > > > _______________________________________________
> > > > > rhq-devel mailing list
> > > > > rhq-devel at lists.fedorahosted.org
> > > > > https://fedorahosted.org/mailman/listinfo/rhq-devel
> > > > >
> > > > _______________________________________________
> > > > rhq-devel mailing list
> > > > rhq-devel at lists.fedorahosted.org
> > > > https://fedorahosted.org/mailman/listinfo/rhq-devel
> > > >
> > > _______________________________________________
> > > rhq-devel mailing list
> > > rhq-devel at lists.fedorahosted.org
> > > https://fedorahosted.org/mailman/listinfo/rhq-devel
> > >
> > _______________________________________________
> > rhq-devel mailing list
> > rhq-devel at lists.fedorahosted.org
> > https://fedorahosted.org/mailman/listinfo/rhq-devel
> >
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/rhq-devel
>
More information about the rhq-devel
mailing list