hi everyone!

i need to get some work done this weekend, and for that i need a working tree. i can't test head since the migration target is broken, and i couldn't figure out what was wrong.

so in order to get a usable test system, i decided to go with revision -r426602 as per thorsten's recommendation on the user list, but it looks like workflow is broken beyond quick repair in that one.

i have absolutely no problem with having my own publications and modules broken time and again, but the default publication should always be in a halfway decent (as in, it displays a page and allows editing and publishing) condition. it hasn't been for over two weeks now.

can someone recommend the most recent revision that is known to work?

it is becoming obvious that it's a mistake to develop fundamental changes in the trunk. this should be discouraged from now on, so that revolutionary work goes in a branch or sandbox or whatever, and other bugfixes can still be applied to the head. once the revolution has settled, we can have one huge merge and everybody is warned and can plunge in head-first. what's happening now is a waste of time and resources. if i downgrade, my findings and improvements will be next-to-useless and will need to be reproduced/ported to head once it's ready, and if i don't, i can't do anything at all.

andreas, my ramblings are not intended to discredit your work - i'm really looking forward to the new code. but what irks me is that i have plenty of time and plenty of motivation to work on lenya atm, and yet all i can do is scratch my balls and worry about my next project deadline.


best,

jörn


--
"Open source takes the bullshit out of software."
        - Charles Ferguson on TechnologyReview.com

--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to