El jue, 31-08-2006 a las 20:05 +0200, Joern Nettingsmeier escribió: > Thorsten Scherler wrote: > > Hi all, > > > > I will now merge back the ac branch into the trunk. This means all > > custom pubs need an update! > > grmbl. > > as much as i appreciate your work, i think you could have asked first. > what's the problem of letting the users decide when to do a svn switch?
Just for the protocol: Well, I asked to test more then a week ago. Not only once, I did it many times. Since I did not get a single reply to this threads I assume lazy consensus. I did all the work in the branch to not break trunk. The merge will *not* break the trunk AFAIK just forces the user to update their ac config file. I gave clear instructions and examples how to update. You ask why, because branches should be merged quickly when stable! > for the first time since mid-june, i've been able to get my project in a > state where it will work well enough to allow basic debugging, and here > goes the next big source of instability. Thanks for calling it like this. It would be not such a "big source of instability" if more people would help to test like Josias did. > > i'd have loved to try the stuff over the weekend *without* being forced > to... hmm, sorry but to be honest if you have a custom project you should use a revision where you know that it is working. Nobody forces you to use HEAD for your project. salu2 > > > When we had > > <world> > > <role id="visit"/> > > </world> > > > > https://svn.apache.org/repos/asf/lenya/sandbox/ac-restricted-1.4-src/pubs/default/config/ac/policies/authoring/index/url-policy.acml > > This would mean now that the access is denied. > > > > So you need to update the subtree-/url-policy.acml to grant the access > > @method="grant". > > See http://svn.apache.org/viewvc?rev=438944&view=rev how I did it for our > > pubs. > > > > Sorry for any inconvenience. > > ~X-[ me, too. > > > I will add some documentation after the merge. > > and how am i supposed to survive in the mean time? guys, your pace is > amazing, but i just can't keep up. and it's really not good engineering > practice to drop in a new, totally unreviewed security-critical > subsystem weeks before a planned release. why can't this be 1.4.1 stuff > in trunk? users who feel adventurous can always svn switch. > -- Thorsten Scherler COO Spain Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
