I would very much like M6 to be released as fast as possible, I think enough time has passed and work done since M5. As for beta - well, I'd like to solve some issues that seem important to me (and probably do some work with ROP&Classic) but I'll be busy until summer at least. So autumn seems realistic date for 3.0
2009/3/30 Andrus Adamchik <[email protected]> > I am +1 on the plan. My availability to do inheritance work is my biggest > concern though. Somewhat predictably I keep digging myself into a deeper and > deeper hole with my day job. Running a company and being a hacker is > obviously incompatible... duh :-/ > > Andrus > > > > On Mar 30, 2009, at 1:08 AM, Aristedes Maniatis wrote: > >> On 30/03/2009, at 4:45 AM, [email protected] wrote: >> >> >>> How many milestone releases are planned before Cayenne 3 going final? >>> (or an approximate timeframe?) >>> >>> It looks that because of the "milestone" label, people can't move to >>> Cayenne 3 :(. >>> >>> I understand that many others use Cayenne 3Mx in production and that is >>> stable(according to them), but unfortunately such decisions are not always >>> in the hands of cayenne users, and for those who decide, "labels" and strict >>> policies are more important :(. >>> >> >> This is good timing that you've raised this since I wanted to open this >> topic as well. Although there are probably a few small bugs that need >> fixing, 3.0 is ready for production use. However there are bits of the API >> which are not yet locked down. >> >> * generics are almost there, but some difficult parts remain such as >> SelectQuery. >> * vertical/horizontal inheritance is close to done >> * Andrey has been talking about work on merging ROP and server classes >> (which would be great!) >> >> Can I propose that 3.0M6 be released during April and then the release >> after that be tagged 3.0beta1 at which time the API is locked down and no >> further non-backward compatible changes made for the life of 3.0. Given a >> couple of months between M6 and b1 and a few more to iron out any bugs in >> the beta process, we'd have a release. >> >> At that point we'd stop supporting 1.2 (under a policy where we support >> the current release and the previous one) and new work would go into 3.1. >> >> What does the team think of these ideas? >> >> >> Ari Maniatis >> >> >> --------------------------> >> ish >> http://www.ish.com.au >> Level 1, 30 Wilson Street Newtown 2042 Australia >> phone +61 2 9550 5001 fax +61 2 9550 4001 >> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A >> >> >> >> >
