[tei-council] release process

[Martin Holmes]

We now have a link-checking tool on Jenkins:

<http://teijenkins.hcmc.uvic.ca/>

It gives output like this:

<http://teijenkins.hcmc.uvic.ca/job/Guidelines-Link-Check/11/parsed_console/>

It takes only about eleven minutes on my Jenkins to check the whole 
Guidelines tree; Sebastian's server is faster, so I expect it'll do 
better there. It's set up to be run manually when we think we're getting 
close to a release.

I've not finished tweaking it yet. Any suggestions for improvements in 
the output are welcome.

There are still one or two bad links left to tidy up...

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
>
>
>
>