I have usually ended up committing the rc number by mistake; hasn't caused any issues for me over several releases. On Apr 22, 2015 10:34 AM, "Steve Hay" <steve.m....@googlemail.com> wrote:
> The current RELEASE notes for Apache::Reload say that after bumping > the version number from X.YY-dev to X.YY-rc1 in the Changes file, this > change should not be committed, and says "(see dev@ archives)" by way > of an explanation. > > However, I have searched the archives and cannot find any explanation > for this bizarre directive. Does anyone know the reason? > > (I'm about to make an RC1 for Apache-Reload so that we can include the > latest code via an official release into the forthcoming > mod_perl-2.0.9.) > > For the record, when I made Apache-Test-1.39, I *did* commit the -rc1 > edit to the Changes file since there was no instruction not to in that > case. I cannot see that any harm has come from it, nor how it could do > in the future. > > We don't bother tagging release candidates, but it might help someone > in the future looking back through the svn history to see which > commits represented different RCs, if anyone is interested. > > Unless I'm overlooking something that anyone can shed some light on > then I will remove the instruction from Apache-Reload before making > RC1. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org > For additional commands, e-mail: dev-h...@perl.apache.org > >
