[tei-council] Release process documentation

[Martin Holmes]

Hi Piotr,

I thought about this, but there is some risk that a local installation 
of the TEI infrastructure might not be fully updated. Sebastian releases 
regular updates to the Debian and Oxygen packages, and obviously keeps 
his Jenkins server updated; he also informs me about any changes such as 
new packages which need to be added, and I try to keep mine in sync too, 
so the two act as a check on each other.

If someone did a local build, and encountered errors, they wouldn't 
necessarily know whether the errors were caused by their local install 
of TEI being slightly out of sync, or whether the errors were real. So 
on balance, relying on the Jinks servers (especially now there are two 
of them) seems the more solid option.

Cheers,
Martin

On 12-02-13 08:00 AM, Piotr Bański wrote:
> Hi Martin,
>
> Thanks for putting the doc together, it's going to be very useful. I
> wonder, maybe it makes sense to encourage local validation before
> waiting for Jenkins to finish, as in the e-mail by Sebastian:
>
> http://lists.village.virginia.edu/pipermail/tei-council/2011/013232.html
>
> Best,
>
>    P.
>
> On 13/02/12 16:47, Martin Holmes wrote:
>> Hi all,
>>
>> I've made one more change to the release process documentation document,
>> TCW22, to add a 17th step relating to the Stylesheets, and arising out
>> of our experience cleaning up after the last release. I've also edited
>> TCW20 to remove the content of the section on Building a Release, and
>> replace it with a link to the new document. The two working papers are here:
>>
>> <http://www.tei-c.org/Activities/Council/Working/tcw20.xml>
>> <http://www.tei-c.org/Activities/Council/Working/tcw22.xml>
>>
>> I think that concludes the work arising out of the 2.0.2 release, and I
>> think we're now in good shape for Gaby to work through TWC22 when he
>> does the next one. Because it's so tricky (well, it's impossible,
>> really) to fully test the process without actually doing it for real, we
>> won't be really sure that the changes we made to avoid the problems we
>> had last time are really effective until the next release, but it should
>> be much smoother next time around.
>>
>> Cheers,
>> Martin
>