[tei-council] Order of release steps

[Gabriel BODARD]

Maybe I'm missing something here (well, I certainly am, but sometimes 
naiveté can lead to valid suggestions) but is the answer not as simple 
as to freeze development, say 24 hours before starting the release, so 
that both the debian packages and all the other TEI materials can be 
generated in this stable time, then the release itself only involves 
changing the version numbers, waiting, testing, and pushing live?

On 20/06/2012 16:44, Martin Holmes wrote:
> True, but unless we have a new build of the deb packages to build with,
> we're building the latest product with an out-of-date version of the deb
> package scripts. They may well not have changed recently, so we get away
> with it, but that's certainly not guaranteed.
>
> Let's say, for instance, that at some point you make a change to teitohtml.
>
>    - In order for that change to be incorporated in a release, it needs
> to be in the deb packages on the Jenkins servers, because when building
> P5 products, Jenkins still uses the teitohtml script which is in the deb
> packages, not the one from SVN.
>
>    - In order to be in the deb packages, the deb packages have to be
> built and released, and updated on Jinks.
>
>    - When they are built and released, they include a complete copy of
> the current state of the P5 products -- which is not a final release;
> it's an interim build. This interim build goes out into the wild to
> every user of deb packages.
>
>     - Then once those deb packages are installed on Jinks, we can build
> the release packages using the changed teitohtml, and then release; but
> at that point, the deb packages have to be built and released again, so
> that they include a fresh build of the P5 products created with the new
> teitohtml.
>
> This is clearly not ideal. And it's a problem that only really exists
> because the Jenkins servers are still dependent on the deb packages to
> build, rather than being able to build P5 products using the latest
> copies of everything (including eg teitohtml) from SVN. I think it's
> worth having another serious attempt at doing what you tried the other day.
>
> If I'm still misunderstanding something in the process above, my apologies.
>
> Cheers,
> Martin
>
>> --
>> Sebastian Rahtz
>> Head of Information and Support Group
>> Oxford University Computing Services
>> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>>
>> Sólo le pido a Dios
>> que el futuro no me sea indiferente
>>
>>
>

-- 
Dr Gabriel BODARD
(Research Associate in Digital Epigraphy)

Department of Digital Humanities
King's College London
26-29 Drury Lane
London WC2B 5RL

Email: gabriel.bodard at kcl.ac.uk
Tel: +44 (0)20 7848 1388
Fax: +44 (0)20 7848 2980

http://www.digitalclassicist.org/
http://www.currentepigraphy.org/