Release tarball....

[Files <fi...@poetryunlimited.com>]

Having read through the dist.sh, and considering some of the emails that we have
received lately, it seems obvious to me that the Mandrake RPMS that I have been
charged with should be able to create their RPMs from the release tarball as well as
the current tree in which the package finds itself.

I have tried to contact Ben Reser, to coordinate with him, and I will be forwarding
everything I find and attempting to synchronize our work.

However, in the meantime, I am a little confused.

There is supposed to be a branch called /branches/release-XXXX - according to dist.
sh

Is this not accessible in a read-only fashion? Or does it exist at all?

Or are the /tags/0.XX.XX the actual release directories?

And lastly, is there a centralized location that houses the release tarballs by
version, instead of only the latest tarball?

Thanks in advance.

Shamim Islam
BA BS


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Release tarball....

[Ben Collins-Sussman <su...@collab.net>]

pll@lanminds.com writes:
 
> /me eagerly awaiting the 'Thumbs up' from the SussMan :)

I sent you the mail yesterday afternoon, did you not see it?  It was
addressed both to you personally, and to the dev list:

------------------------

Sender: sussman@kepler.ch.collab.net
To: dev@subversion.tigris.org, Paul Lussier <pl...@mindspring.com>,
    Paul Lussier <pl...@lanminds.com>
Subject: Re: svn commit: rev 7136 - in trunk: . subversion/include
References: <20...@svn.collab.net>
From: Ben Collins-Sussman <su...@collab.net>
Date: 22 Sep 2003 13:19:12 -0500
In-Reply-To: <20...@svn.collab.net>
Message-ID: <m3...@kepler.ch.collab.net>
Lines: 17
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

sussman@tigris.org writes:

> Author: sussman
> Date: Mon Sep 22 13:05:42 2003
> New Revision: 7136
> 
> * CHANGES:   new 0.30 changes.
> * svn_version.h (SVN_VER_MINOR): bump to 0.30.0

There ya go, Paul.  You can create your 0.30.0 release branch from
(r7136, /trunk).

Also, all the documentation on http://svnbook.red-bean.com is fully
up-to-date (as of r7135).  So you can pull down the huge PDF and HTML
files from there into your tarball.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Release tarball....

[pl...@lanminds.com]

>>>>> On 23 Sep 2003, "Ben" == Ben Collins-Sussman wrote:

  Ben> Typically this happens a few days after the code-complete date.
  Ben> At the moment, Paul Lussier is working on this process.  He
  Ben> simply hasn't made the branch yet.

And here's why :)

>>>>> On Mon, 22 Sep 2003, "kfogel" == kfogel@collab.net wrote:

  kfogel> Ben's volunteered to write the CHANGES file, so you might
  kfogel> want to wait for that too.  He'll do it right after the cert
  kfogel> commit.

  pll> Okay, can someone ping me (here or privately) when this is
  pll> ready.  I'm just back from a week away, and have a ton of stuff
  pll> to catch up on.

  kfogel> Okay, Ben will send you a personal mail when ready.

/me eagerly awaiting the 'Thumbs up' from the SussMan :)
-- 
Seeya,
Paul

GPG Key fingerprint = 1660 FECC 5D21 D286 F853  E808 BB07 9239 53F1 28EE

	 If you're not having fun, you're not doing it right!



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Release tarball....

[Ben Collins-Sussman <su...@collab.net>]

"Files" <fi...@poetryunlimited.com> writes:

> There is supposed to be a branch called /branches/release-XXXX -
> according to dist.  sh
> 
> Is this not accessible in a read-only fashion? Or does it exist at all?
> 
> Or are the /tags/0.XX.XX the actual release directories?

When we finish a milestone (in terms of code-completion), we update
the CHANGES file and bump svn_version.h.  Then we ask the release
manager to make a release.  The procedure is documented in notes/releases.txt.

The release manager creates the release branch, tests it, rolls a
tarball from it, and finally moves the release branch to a tag.

Typically this happens a few days after the code-complete date.  At
the moment, Paul Lussier is working on this process.  He simply hasn't
made the branch yet.

> Andreates lastly, is there a centralized location that houses the
> release tarballs by version, instead of only the latest tarball?

  http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=260


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org