[tei-council] access to current builds of TEI P5

[Kevin Hawkins]

On 1/27/2011 1:18 PM, Sebastian Rahtz wrote:
> On 27 Jan 2011, at 14:27, Kevin Hawkins wrote:
>
>> Okay.  So, Laurent and Sebastian, what would you like us Council members
>> to look at or comment on regarding Hudson?  We can see a web
>> presentation of the automation, plus a working release of files, but
>> what can you use our help investigating?
>
>
> The point of the Hudson setup is to enable people other than me or Lou
> to make changes to the Guidelines without them having to implement a complete
> build and test environment locally. No more, no less. All you need to grok
> is Subversion.
>
> So let's take Tite as an example. If you edit and commit the master tei_tite.odd file
> on Sourceforge, and wait an hour for Hudson to notice, do you get
> feedback enough to see that you have not made mistakes, and
> enough generate files to let you test things?
>
> Next week I will have a job on Hudson to automate a deployment
> of a new release (I hope). If that works, it will mean that all anyone
> needs to make a release is to edit files in SF, and then press the button in
> Hudson. (please dont try this at home yet...)

This all makes sense, and I understand the goal of Hudson.  I don't have 
access to commit changes in SourceForge, and they only people I know of 
on Council who do are Sebastian and Lou.  (Perhaps there are others.) 
So I believe I am disqualified from testing at this time.

--K.