[tei-council] gearing up for release 2.6.0

[Martin Holmes]

Hi Peter,

On 14-01-18 02:47 PM, Peter Stadler wrote:
> Dear all,
>
> this is to officially remind you of the upcoming release which we
> decided to be carried out next Monday (i.e. the day after tomorrow!)
> I (Peter, ‚special status release technician‘) plan to start things
> in the morning around 9 AM (CET). It’s been calm at tei at sourceforge
> in the last days so I assume that everyone is actually aware of this
> date and paused his/her work.
>
> Now the unofficial part. I’m a little bit nervous and appreciate any
> hand that will hold mine (not the whole day, but it’d be good to know
> someone (from Oxford?) being around). BTW, is the #tei-c IRC channel
> the best way to reach out for help since I’ve never seen someone
> around there? Or shall I send an email?

People will definitely be there from early in the day in Europe, and 
then later in the day (if the process drags on for some reason) I'll 
show up before 5pm your time.

> Additionally some questions that came up: *
> P5/ReleaseNotes/readme-2.6.0.xml: is this considered complete by
> now?

That's a question for James, I think.

> * item 7 from
> http://www.tei-c.org/Activities/Council/Working/tcw22.xml seems
> outdated.

I think you're right. We used to have a system where you logged in as 
yourself, and they su-ed to "become" tei, but if we're now logging in as 
tei, that's unnecessary. James, David, Sebastian et al: should I change 
step 7 in the step-by-step instructions:

<http://www.tei-c.org/Activities/Council/Working/tcw22.xml#releaseSteps>

so instead of this:

ssh [youraccount]@tei-c.org
sudo sutei (this should put you in the /home/tei directory)

we have this:

ssh tei at tei-c.org

> ** I already log in as user tei and I’m not able to sudo
> (asks for password). Question 1: Do I need su power?

I'm pretty sure you don't.

> ** I do not find
> a bin directory and svnUp.sh. What I do find is the TEI svn subtree
> „P5“ at /var/www/vhosts/tei-c.org/private/P5. Question 2: Is a simple
> ‚svn up‘ on that directory enough? * tei-database-rebuild.sh: I think
> the hostname case switch must be adjusted

This looks like a major change from the original server setup. When you 
log in as tei, where do you find yourself? (pwd)
>
> Some proposed changes to tcw22.xml so far: * "What you will need
> before you start“, item 2 (Shell access on the TEI SourceForge
> project) I propose to join this item with with 3 and 7 (well, not in
> one item but to have these in a sequence) and to add a line to the
> last one (or even a new item): Test it by trying to log in via ‚ssh
> sfuser,tei at frs.sourceforge.net‘ *from* the tei server. That should
> *not* prompt for a password while echoing „Welcome! This is a
> restricted Shell Account. You can only copy files to/from here.“ *

Is "tei" a user on SourceForge? I didn't think so. I thought you had to 
use your own SourceForge credentials there, hence the instruction to set 
up ssh access.

> "Step-by-step instructions“, item 1 ("Ensure that
> P5/ReleaseNotes/readme-X.X.X.xml has been written“). The next line
> declares this to be an uncommon procedure since the TEI Council chair
> should have already create that file.

You should definitely look at that file one last time and make sure it's 
OK. At least twice in the last few years the release process has had to 
be repeated because of typos or omissions in that file. :-)

> So, it seems to me the actual
> issue for the release technician is to simply remove the „beta“ from
> the version number which can easily be forgotten when you are not
> looking closely at the following paragraph.

That seems correct in the instructions to me. It has its own complete step:

<quote>
Edit the P5/VERSION file to the correct number
This file consists only of the bare version number, followed by "alpha" 
or "beta":
2.8.2beta
For the release process, you need to remove the letters from the end, 
leaving a pure version number:
2.8.2
This changes the release from beta (or possibly alpha) to the actual 
release version number. After the release process has been completed, 
the number should be incremented appropriately, and "alpha" added to the 
end of it:
2.8.3alpha
signifying that the versions built subsequent to the release are now in 
the alpha stage.
</quote>

> I propose to change the
> heading to "remove „beta“ from P5/ReleaseNotes/readme-X.X.X.xml
> version number“ and emphasize this procedure in the first
> paragraph.

If you think that's clearer, we can certainly do that.

>The edge case of creating that file can be discussed
> subsequently.

Rather than checking that it's there, the step should be to check that 
it's correct and complete.

Cheers,
Martin

>
> Many thanks in advance and all the best Peter
>
>
>
>
>
>