Ralph Goers wrote:
Ben Pope wrote:
It makes very little sense to mark it stable without it actually being
what is generally considered (by this community) as stable.
You might as well just throw away all semantics, I doubt there are
many people here who want to release something whose API they know
will change, and then have to support it. With all due respect, you've
been around here long enough to know that you have to scratch your own
itches or wait for somebody else to.
Yes. I understand that. What I don't understand is that we have killed
off the alternative forms blocks and have been telling folks to use
CForms. But at the same time we are telling them that it is not
stable. In effect, this means we are telling our customers that Cocoon
as a whole is not stable because it does not have a stable forms
framework. And while I haven't yet wandered into the code in CForms I
care greatly how Cocoon is perceived by our customers.
Now CForms has been under development for quite some time. I find it
hard to believe that if the problems that are left were so serious that
it makes the framework unusable in a production environment that they
wouldn't have been fixed by now.
The bottom line is you cannot have code sitting around forever telling
people its great but you have to use it at your own risk cause we might
change it anytime we feel like it. This has just been going on for far
too long. The code is never going to be perfect.
So either a) formally support what is being delivered or b) fix it so it
can be supported. Otherwise we need to find a forms framework that can
be supported.
+1
CForms has been "nearly stable" for two years. Obviously no one of us
care enough about the remaining and, AFAIU well documented API "issues",
to do anything about it, so question is if they really are that important.
And as so many people allready depend on the current API we have to
treat it as stable anyway. We can't introduce incompabilities at a whim
anymore.
As I have said before
http://marc.theaimsgroup.com/?t=111675871100002&r=1&w=2 our current
release policy just doesn't work anymore. We have so high requirements
on perfection so that we have stoped marking things as stable or release
anything any longer.
Open source software becomes good because people who use it want it to
become good and spend time to make it happen. But instead we warn
everyone to depend on anything new and thus neither get feedback on what
we do or motivation to finish it.
/Daniel
- Re: Marking cforms stable in 2.1.8 Daniel Fagerstrom
-
