[tei-council] Commit Freeze before Release 2.20
Martin Holmes
mholmes at uvic.ca
Thu Oct 25 14:16:55 EDT 2012
It's OK right now -- I kicked off a second P5-Test build. After all this
is over, I'm going to nuke that workspace. I don't know what the problem
is there, but one possibility is memory allocation to jing. I'll have to
compare your settings to mine. But my server is 64-bit and yours is
32-bit, IIRC, so my memory allocations may have to be more generous.
Cheers,
Martin
On 12-10-25 10:51 AM, Sebastian Rahtz wrote:
>
> On 25 Oct 2012, at 18:47, James Cummings <James.Cummings at it.ox.ac.uk>
> wrote:
>
>> On 25/10/12 17:47, Sebastian Rahtz wrote:
>>>> Please do *NOT* commit anything to sourceforge (unless your name
>>>> is Piotr) until after the release is announced.
>>> i have to change Stylesheets, sorry. New bug report from Louis Dubeau
>>> is catastrophic (it loses attributes). i am very dismayed my tests didn't catch it
>>
>> Understood, we'll proceed assuming that all your changes will
>> work, but hold off on final release until they do.
>
>
> Oxford jenkins appears to be heading up the home straight now with
> no problems. but I am worried that uvic seems to yoyo between
> success and failure with the stack overflow. I can't see a pattern there.
> --
> Sebastian Rahtz
> Director (Research Support) of Academic IT Services
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>
--
Martin Holmes
University of Victoria Humanities Computing and Media Centre
(mholmes at uvic.ca)
More information about the tei-council
mailing list