[PATCH 2/2] releasing: Add example commands to release directions

[Bryce Harrington]

On Wed, Jan 07, 2015 at 10:11:29AM +1000, Peter Hutterer wrote:
> On Tue, Jan 06, 2015 at 02:08:39PM -0800, Bryce Harrington wrote:
> also, the xorg release script was modified a while ago to support
> wayland/weston. as much as a step-by-step instruction is useful, having
> everyone run the same script is the best approach :)
> http://cgit.freedesktop.org/xorg/util/modular/tree/release.sh

Ah, okay.  With one fix, the dry-run seems to work fine here, so I'll
reroll the patchset with this in place of the relevant steps.

Bryce

> with that it's just step 0, then
>     $ path/to/release.sh .
> email using the .announce file as template
> and continue with step 8
> 
> Cheers,
>    Peter
> 
> >  
> > -  6.  Push configure.ac commits and tags.
> > +  3.  Create the tarballs
> >  
> > -  7.  Send out release announcement.
> > +      $ make distcheck
> >  
> > -  8.  Get the release email URL from
> > +      (If distcheck isn't passing, such as if Wayland's testsuite is
> > +      failing, you can skip testing via `TESTS= make distcheck`.  Or,
> > +      if you must, bypass checking entirely via `make dist`.)
> > +
> > +  4.  Publish the tarballs
> > +
> > +      $ scp <tarballs> annarchy.freedesktop.org:/srv/wayland.freedesktop.org/www/releases/
> > +
> > +  5.  Compose a release announcement with the SHA1's, tagged commits,
> > +      and notable changes.  For x.y.0 releases, indicate
> > +      the schedule for the x.y+1.0 release.
> > +
> > +      $ sha1sum <tarballs>
> > +
> > +  6.  Push configure.ac commits and tags
> > +
> > +      $ git push origin master 1.7.0
> > +
> > +  7.  Send the release announcement to wayland-devel at lists.freedesktop.org
> > +
> > +  8.  Get your freshly posted release email URL from
> >        http://lists.freedesktop.org/archives/wayland-devel/
> >  
> >    9.  Update releases.html in wayland-web with links to tarballs and
> > -      release email.
> > +      the release email URL
> >  
> > -  10. Update topic in #wayland to point to release announcement
> > +  10. Update topic in #wayland to point to the release announcement URL
> >  
> >  For x.y.0 releases, also create the x.y branch.  The x.y branch is for
> >  bug fixes and conservative changes to the x.y.0 release, and is where
> > @@ -34,6 +55,9 @@ fixing for the x.y.1 release for a little longer) or before the x.y.0
> >  release (like we did with the 1.5.0 release, to unblock master
> >  development early). 
> >  
> > +    $ git branch x.y
> > +    $ git push origin x.y
> > +
> >  The master branch configure.ac version should always be (at least)
> >  x.y.90, with x.y being the most recent stable branch.  Stable branch
> >  configure version is just whatever was most recently released from
> > -- 
> > 1.9.1
> > 
> > _______________________________________________
> > wayland-devel mailing list
> > wayland-devel at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/wayland-devel
> > 
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel