Michael Wechner wrote: > Jörn Nettingsmeier wrote: > >> hi everyone! >> >> first of all, a happy new year to everyone. after a couple weeks off, >> i'm back.
The same to you and welcome back :-) >> apologies for disappearing for so long after the usecases handler >> rewrite - i'll look into the remaining bug reports over the next few >> days. >> >> the reason i was silent for a while was that i had to write off a >> rather major project i was doing, because it became evident that lenya >> 1.4 has not reached a level of maturity where it could be deployed to >> > 100 users and still let me sleep soundly at night. moreover, i had - >> and still have - serious doubts about the long-term sustainabilty of >> the lenya ecosystem, which was the main reason to pull the emergency >> brake. bugs can be fixed, but an unsustainable community is very hard >> to work around. > > > the ecosystem is a result of the quality of Lenya. If Lenya is no good, > then people will not use it and hence people will not join the ecosystem. > I tried many times to explain what I think needs to be done to make > Lenya good, but people disagreed resp. just did something else. > That's ok with me, because I don't need to be proven right and I don't > have to be the one ruling this community. > I am not sure whether the quality is the reason. At least 1.4 seems to be better than 1.2. However, i must confess that i am not really an 1.4 expert :-( According to my opinion the problem is rather an usual problem of software projects: Too many features are added to the first 1.4 release (usecase framework, modules, publication templating ......). For further releases (if there are any) we should clearly define the feature we want and postpone others to a next release. > It's just sad to hear that you seem to experience what I had experienced > more than a year ago and I can only hope that some people > learn from that. [ ... ] > >> first, that a bunch of 1.2 users and developers really need to get >> their act together and get 1.2 out the door. i cannot understand why >> this is not happening, especially there seem to people running a >> business based on 1.2. (and no, i won't learn the fscking legacy >> codebase to help with that.) > > > there is not much to do except create a tarball of 1.2.5-dev and test it > as good as possible and if people agree of the quality, then release this > tarball. > Gregor offer to do a 1.2.5 release but there was hardly any feedback. That is really strange and shows the actual state of the community. BTW at the moment there is almost only Andreas writing code for 1.4 Jann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
