[Bf-committers] libraries and release tagging

Martin Poirier theeth at yahoo.com
Sun Jun 6 03:47:13 CEST 2010

--- On Sat, 6/5/10, Benjamin Tolputt <btolputt at internode.on.net> wrote:

> From: Benjamin Tolputt <btolputt at internode.on.net>
> Subject: Re: [Bf-committers] libraries and release tagging
> To: "bf-blender developers" <bf-committers at blender.org>
> Received: Saturday, June 5, 2010, 8:41 PM
> Martin Poirier wrote:
> > Even if the libs themselves aren't tagged, anyone who
> wants to build a past release can just do a checkout of the
> lib tree with the revision matching the release tag.
> >
> > Look there [1], you can easily see what revision
> matches each release, than you can just do
> >
> > svn checkout --revision <NUMBER> https://svn.blender.org/svnroot/bf-blender/trunk/lib
> >
> > [1] http://projects.blender.org/plugins/scmsvn/viewcvs.php/tags/?root=bf-blender
> >
> > I really don't feel like a tag is needed, to be
> honest.
> >   
> A tag isn't necessarily needed once you know the revision
> of a release
> either - we still do that for the convenience of developers
> who want to
> build an old release without knowing every step of the
> development history.

The release tags are first and foremost useful to make sure that all release builds are done with the same revision.

> If it is possible, I think tagging the library revisions
> with the
> appropriate label is a small effort that has no ongoing
> issues affecting
> the current/future development of Blender. Not doing it
> (provided it is
> possible) would come across as just being stubborn for no
> fixed benefit.

Libs for 2.49 are already tagged (they would most likely also work for 2.48 and some other previous versions).

For future releases, we'll tag both (all of trunk), no problem.


More information about the Bf-committers mailing list