[tei-council] Release notes (was Re: next release?)

[Kevin Hawkins]

All,

I'm about to adjust tcw22 based on this and a few more emails sent in 
the past few days to make the instructions clearer.  Notes below, 
including some questions for Gabby and requests from anyone for 
clarification ...

On 6/18/12 1:34 PM, Gabriel BODARD wrote:
> 2. Version numbers updated. (I had to stop and think for a moment
> whether I was supposed to be updated the -fr version as well. Obviously
> yes, but just to note that with current wording I wondered.)

I'm not sure how to improve on the current wording.  Could you suggest 
something?

> 4. Debian changelogs: the changelog files don't exist where they are
> listed in the sbs. I now understand that this is automated in Jenkins...
> so this point should be deleted from the doc.

I've commented it out (and added a comment explaining that Jenkins now 
does it).

> 7. This all seems okay to me, but I think the item in the doc could be
> spelled out a bit more explicitly what to look for.

Suggestions?

> 8. Apparent problem with instructions in this item:
>
> svnUp.sh runs as written, but
> tei-install.sh needs the "sh" command before it. (Does this mean it is
> not executable?) Either that needs to be changed, or the instructions.
> (Note: James has already fixed the file so it is executable by user.)

Right, the problem was that it's not executable.  I hesitate to insert 
the "sh" command because maybe the script was written to assume you use 
csh or bash or something.  Best to leave the instructions as they are, 
in my opinion.

> Also: Sourceforge denied me permission to make the release at this step.
> We need to add a note that the user needs to add the public key from
> /home/tei/.ssh/id_dsa to their Sourceforge account before they can rsync
> the release zip. This probably belongs in the "What you need" section at
> the top of tcw22.

So I could add this to the "what you need" section:

* A copy of public key from tei-c.org:/home/tei/.ssh/id_dsa at ~/.ssh/ 
in your Sourceforge account's home directly. This is need to rsync the 
release zip.

Is that correct?  It seems to me that if you use your SF for anything 
else, this could overwrite keypairs that you might have on file.  But I 
guess if you're that advanced, you'll know how to do this properly. 
Still, I recommend suggestions on a better way to do this.

> 10. Defaults set. Fine. (Instructions could be clearer--I've done this
> before for other projects, but if not I might not have known where to look.)

Can you suggest a clarification?

> 12. Sebastian informed that debian can be released.
>
> 13. Sebastian informed that oxygen-tei can be updated.
>
> 14. Checking TEI website and downloads. (I wonder we shouldn't do this
> check before the previous two, and maybe before 10 as well. If there's a
> problem with the website we may have to start again.)

If someone tells me to move this step, I will gladly do it.

--Kevin