Re: Release plans?
Mike South <[email protected]> Thu, 27 Mar 2014 14:47:51 -0500
| Newsgroups | gmane.comp.lang.perl.modules.lwp |
|---|---|
| Message-ID | <CAN483vczWzc92vt=aa=hkuXvu2922KssxGunXjCV05V780oQLw@mail.gmail.com> |
--001a11c2efb84eb11a04f59bdc48 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Mar 24, 2014 at 5:27 PM, Gisle Aas <[email protected]> wrote: > My release procedure has been: > > - Increment version number in Makefile.PL > - Check that all updated module files have a version number that match > the new release: grep VERSION $(git diff --name-only 6.05) > - Paste "git shortlog -n 6.05.." into the Changes file, and edit it > until it looks good (enough). > - make dist > - upload the tarball > > > > I would suggest that you create a file called release_process, put the above in it, commit to repo (or add to the README or whatever appropriate file), so the knowledge doesn't get lost. mike --001a11c2efb84eb11a04f59bdc48 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail= _quote">On Mon, Mar 24, 2014 at 5:27 PM, Gisle Aas <span dir=3D"ltr"><<a= href=3D"mailto:[email protected]" target=3D"_blank">gisle@activestate.= com</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div dir=3D"ltr">My release procedure has be= en:<div><br><div>=A0 - Increment version number in Makefile.PL<br><div>=A0 = - Check that all updated module files have a version number that match the = new release: grep VERSION $(git diff --name-only 6.05)=A0</div> <div>=A0 - Paste "git shortlog -n 6.05.." into the Changes file, = and edit it until it looks good (enough).</div><div>=A0 - make dist</div><d= iv>=A0 - upload the tarball</div><div><br></div><div><br></div></div></div>= </div> <div class=3D"HOEnZb"><div class=3D"h5"> <div class=3D"gmail_extra"><br></div></div></div></blockquote><div><br></di= v><div>I would suggest that you create a file called release_process, put t= he above in it, commit to repo (or add to the README or whatever appropriat= e file), so the knowledge doesn't get lost.</div> <div><br></div><div>mike</div></div></div></div> --001a11c2efb84eb11a04f59bdc48--