I guess my experience may not be a good example to follow everywhere, but I have a major production deployment using fresh trunk builds of Cayenne (meaning right now it is newer than even 3.2M1). This is dozens of sites, millions of users.
For us it takes some effort to upgrade the code to new APIs between the builds (and occasionally we leave some deprecated code behind), but I don't recall the core giving any trouble that can be attributed to the most recent changes. Maybe it did once or twice in the last ~3 years. As for 3.1, IMO it is certainly production-ready. DI part is rock-solid, etc. Andrus On Jul 23, 2013, at 11:19 AM, Aristedes Maniatis <[email protected]> wrote: > On 23/07/13 5:57pm, Malcolm Edgar wrote: >> The quality of Cayenne is extremely high, so I am not concerned about the >> label we give the release, but I want understand peoples experience with >> 3.1, is it ready for prime time? > > I've been using 3.1 in production ever since 3.1M1. We are just now thinking > about getting 3.2M1 into our development so that we move it into production > in the next three months. This is for six web applications and one ROP Swing > application used by about 300 internal people in total across multiple > organisations (plus taking 250,000 enrolments per year from the general > public). > > We've had a small number of issues in Cayenne, but almost always us bumping > up against features we'd like to have rather than bugs. > > Ari > > > -- > --------------------------> > Aristedes Maniatis > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
