public inbox for frysk-cvs@sourceware.org
help / color / mirror / Atom feed
From: cagney@sourceware.org
To: frysk-cvs@sourceware.org
Subject: [SCM] master: Add a page on releasing frysk.
Date: Thu, 03 Apr 2008 17:28:00 -0000 [thread overview]
Message-ID: <20080403172804.25200.qmail@sourceware.org> (raw)
The branch, master has been updated
via 9ad78696423af289ada0ff136fe39a9794760d61 (commit)
from dcf34054390b012ad1442d7fd022db5ef46d9850 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email.
- Log -----------------------------------------------------------------
commit 9ad78696423af289ada0ff136fe39a9794760d61
Author: Andrew Cagney <cagney@redhat.com>
Date: Thu Apr 3 13:27:42 2008 -0400
Add a page on releasing frysk.
-----------------------------------------------------------------------
Summary of changes:
htdocs/documentation/index.html | 3 +
htdocs/releases/index.html | 189 +++++++++++++++++++++++++++++++++++++++
2 files changed, 192 insertions(+), 0 deletions(-)
create mode 100755 htdocs/releases/index.html
First 500 lines of diff:
diff --git a/htdocs/documentation/index.html b/htdocs/documentation/index.html
index b540a79..a4f5d3d 100755
--- a/htdocs/documentation/index.html
+++ b/htdocs/documentation/index.html
@@ -105,6 +105,9 @@ information</a> for <span style="font-style: italic;">frysk </span>using
the gcov/lcov test coverage tools.<br>
</li>
+<li>For how to create a <em>frysk</em> release, see
+the <a href="../releases">releases</a> page.</li>
+
</ul>
diff --git a/htdocs/releases/index.html b/htdocs/releases/index.html
new file mode 100755
index 0000000..4189c0f
--- /dev/null
+++ b/htdocs/releases/index.html
@@ -0,0 +1,189 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+
+<html>
+ <head>
+ <title>Frysk System Monitor / Debugger: Making a Release</title>
+ <link rel="stylesheet" href="../frysk.css" type="text/css">
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+ <meta http-equiv="Content-Style-Type" content="text/css">
+ </head>
+
+ <body>
+ <table cellspacing="2" cellpadding="2" border="0" width="100%">
+ <tr>
+ <td valign="bottom" height="80">
+ <img src="../frysklogo.png" alt="Frysk logo">
+ </td>
+ <td valign="bottom" class="topnavright" align="right">
+ <a href="../">Home</a>
+ |
+ <a href="../wiki/">Wiki</a>
+ |
+ <a href="../usecases/">Use Cases</a>
+ |
+ <a href="../workflow/">Work Flows</a>
+ |
+ <a href="../questions/">FAQ</a>
+ |
+ <a href="../getinvolved/">Get Involved</a>
+ |
+ <a href="../bugzilla/">Bugzilla</a>
+ |
+ <a href="../build/">Build</a>
+ |
+ <a href="http://planet.fryskproject.org">Blog</a>
+ |
+ Documentation
+ </td>
+ </tr>
+ </table>
+ <div class="mainbackground">
+ <div class="maintextregion">
+ <img src="../fryskcorner.gif" alt="triangle">
+ <table cellspacing="2" cellpadding="4" border="0" width="99%" style="margin-top:17px;">
+ <tr>
+ <td width="200" valign="top" align="left">
+
+ </td>
+ <td valign="bottom">
+<!-- start title -->
+ <h1>Making A Release</h1>
+ <!-- end title -->
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">
+ <!-- start logo -->
+<p>
+<a href="#branch">Branch</a><br>
+<a href="#release">Release</a>
+</p>
+ <!-- end logo -->
+ </td>
+ <td valign="top">
+ <!-- start text -->
+
+<p><em>frysk</em> is making point release, cut from the Git
+repository's <tt>HEAD</tt>, on the first Wednesday of each month.
+This lets us deliver new features quickly, with a relatively low
+overhead.</p>
+
+<p>The relese branch is taken on the first Wednesday at <tt>00:00
+GMT</tt>, just in time for <em>frysk</em>'s Wednesday meeting. We
+then, during the meeting, conduct a brief review, check the NEWS file,
+and make a go/no-go decision. It is then pushed out, perhaps with a
+few minor fixes.</p>
+
+<p>The process is also relatively simplistic. It assumes for
+instance:
+
+<ul>
+<li>there's never a pre-release tar-ball<br>that would require extra
+pre-release version numbers such as <tt>0.1.90</tt>... and then only
+at the last moment set the real version (<tt>0.2</tt>).
+</li>
+<li>if there's ever a need for a re-spin, it just gets assigned a
+patch-level number like <tt>0.2.1</tt> and use the original releases
+branch</li>
+</ul>
+
+<a name="branch"><h2>Cutting the Branch</h2></a>
+
+<p>Here's a suggested sequence:</p>
+
+<ul>
+
+<li>To make things easier, first lets set up a few standard shell
+variables; you'll want to set version to something more
+meaningful:
+
+<pre>
+version=0.2 ! ! ! change this
+echo $version
+date=`date -u +"%Y.%m.%d"`
+echo date=$date 1>&2
+shar1=`git-rev-list --before=$date -n1 HEAD`
+echo shar1=$shar1 1>&2
+branch=frysk/$version
+echo $branch
+</pre>
+</li>
+
+<li>Next we create a branch (frysk release branches are named
+frysk/<version>), and push that upstream:
+
+<pre>
+echo branch=$branch shar1=$shar1
+git branch $branch $shar1
+git push origin $branch
+</pre>
+</li>
+
+<li>Finally, we update the version number of the branch, and push
+that:
+<pre>
+git checkout $branch
+echo $version > common/version.in
+cat common/version.in
+git add common/version.in
+git commit -m "Set version.in to $version"
+git push origin
+</pre>
+</li>
+
+</ul>
+
+<p>The branch can then be checked out by everyone and build locally.
+Of course the keen will have already checked out the branch point
+using something like:
+
+<pre>
+git checkout `git-rev-list --before='00:00 GMT' -n1 HEAD`
+</pre>
+
+<a name="release"><h2>Making the Release</h2></a>
+
+<p>Here's a sequence for releasing frysk, we're assuming that $version
+was set above:
+
+<ul>
+
+<li>First lets create a tar ball from the head of the branch. It's a
+little convoluted since it find's the branch head's shar1 and then
+uses that.
+
+<pre>
+echo version=$version branch=$branch
+shar1=`git-rev-list -n1 $branch`
+echo shar1=$shar1
+rm -rf frysk-$version
+git archive --prefix=frysk-$version/ $shar1 | tar xpf -
+tar cfj frysk-$version.tar.bz2 frysk-$version
+</pre>
+</li>
+
+<li>Assuming you're happy with that, tag the release:
+<pre>
+git tag -u <gpg-name> -m frysk-$version $shar1
+git push --tags
+</pre>
+</li>
+
+</ul>
+
+ <!-- end text -->
+ <p> </p>
+ </td>
+ </tr>
+ </table>
+ </div>
+ </div>
+ <table cellspacing="2" cellpadding="2" border="0" width="100%">
+ <tr>
+ <td align="center" class="footer">
+ <a href="http://sources.redhat.com">sources.redhat.com</a>
+ </td>
+ </tr>
+ </table>
+ </body>
+</html>
hooks/post-receive
--
frysk system monitor/debugger
reply other threads:[~2008-04-03 17:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080403172804.25200.qmail@sourceware.org \
--to=cagney@sourceware.org \
--cc=frysk-cvs@sourceware.org \
--cc=frysk@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).