[tei-council] Order of release steps

[Martin Holmes]

Blast, I forgot that the actual products are also in the deb packages. I 
was thinking of them only being the required scripts (teitohtml etc.).

This is more messed up than I thought it was, then. We can't do 
everything without doing everything first. We have to build and install 
the deb packages, then build the products with them, then build and 
distribute new versions of the deb packages.

In which case, the real requirement is to make it possible for Jinks to 
build the products without any dependency on the installed deb packages 
at all. That's what Sebastian started trying to do the other day, but 
gave up. But that's where we have to go, I think.

Cheers,
Martin

On 12-06-20 06:26 AM, Lou Burnard wrote:
> On 20/06/12 13:54, Martin Holmes wrote:
>> I woke at 4am with an attack of the bleedin obvious.
>
> You probably want to forego that extra helping of cheese after dinner...
>>
>> It seems to me that the first actions following the SVN freeze and the
>> update of the version number by the release technician should be the
>> update of the Debian packages.
>
> Eh? Shurely this is backwards? The deb packages are a way of
> distributing the release, argal they are a version of it, argal they
> can't be created until it is finalised, in all its raging glory.
>
> It's true that we use the deb packages to build the build environment
> (such is the glorious recursivity of the tei) but conceptually at least,
> we should be using the packages from release n-1 to build release.
>

-- 
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)