[tei-council] release process

[Martin Holmes]

???you're idea is a good one???

sed "s/you're/your/"

On 14-01-23 05:51 AM, Martin Holmes wrote:
> We have been working on an automated link-checking system to run
> (manually) as a Jenkins job prior to release. That will be up and
> running in the next few days. Meanwhile, using results from testing,
> I've fixed about 70 broken links in the P5 source.
>
> Nevertheless, I think you're idea is a good one -- this time it was
> broken links, but next time it will be something else...
>
> Cheers,
> Martin
>
> On 14-01-23 04:13 AM, Peter Stadler wrote:
>> Dear all,
>>
>> during the release process of 2.6.0 we had to roll back to release 2.5.0 at some stage because we found some broken links in the HTML version of the Guidelines. Call me conservative, but I think it might be a good idea to
>> 1. upload the new Guidelines to tei-c.org
>> 2. Check the release
>> 3. AND THEN symlink ‚current‘ to point at the new release
>>
>> We could insert a simple ‚read -p‘ after line 60 in tei-install.sh or even split the script in two (three)
>> * upload2tei-c
>> * make-current
>> * upload2sf
>>
>> Comments?
>> Peter
>>
>>
>>
>>