You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by jo...@yahoo.com on 2009/03/29 19:45:33 UTC
How manay milestones before 3.0 final?
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 :(.
thanks,
Joseph.
Re: How manay milestones before 3.0 final?
Posted by Andrus Adamchik <an...@objectstyle.org>.
Thanks for the reminder. I reclassified CAY-1164. It does need more
work indeed.
Andrus
On Mar 30, 2009, at 8:01 PM, Robert Zeigler wrote:
> The EJBQLQuery pane in the modeler appears to need some work, as
> well; I haven't played with it extensively, but I put entered a
> valid query and was informed by the modeler that the query was
> invalid (I use the exact same query in my application with no
> issues)... haven't filed an issue for this yet as I haven't had time
> to look into it deeper (maybe there /was/ an issue with my
> query. :) I'd prefer that to be taken care of before an M6 release,
> at least. I'll see if I can look into it today and file an issue, if
> appropriate.
Re: How manay milestones before 3.0 final?
Posted by Robert Zeigler <ro...@gmail.com>.
Cleaned out my repo, checked the project out fresh, rebuilt clean,
still seeing problems; out of time right now, but I'll look at it
again later today .
Robert
On Apr 3, 2009, at 4/39:41 AM , Robert Zeigler wrote:
> Tried a mvn clean; mvn install before posting.
> But it's still possible that I was picking up an older build; I'll
> clean out the 3.0 branch of my local repo to be sure.
>
> Robert
>
> On Apr 3, 2009, at 4/34:50 AM , Andrus Adamchik wrote:
>
>> Hmm... works for me. Can you make sure you have the latest clean
>> build, as some parser classes were regenerated, so "mvn clean" is
>> needed.
>>
>> Andrus
>>
>>
>> On Apr 3, 2009, at 12:36 PM, Robert Zeigler wrote:
>>
>>> Still having issues.
>>>
>>> Even with a very basic query:
>>> select pr from ProtocolRun pr
>>>
>>> I get the following message:
>>> "Encountered " "pr"" at line 1, column 35
>>> Was expecting one of:
>>> ","...
>>> "ORDER"...
>>> "WHERE"...
>>> "GROUP"...
>>> "HAVING"...
>>> "LEFT"...
>>> "INNER"...
>>> "JOIN"...
>>>
>>>
>>> Robert
>>>
>>> On Apr 3, 2009, at 4/31:41 AM , Andrus Adamchik wrote:
>>>
>>>>
>>>> On Mar 30, 2009, at 8:01 PM, Robert Zeigler wrote:
>>>>
>>>>> The EJBQLQuery pane in the modeler appears to need some work, as
>>>>> well; I haven't played with it extensively, but I put entered a
>>>>> valid query and was informed by the modeler that the query was
>>>>> invalid (I use the exact same query in my application with no
>>>>> issues)... haven't filed an issue for this yet as I haven't had
>>>>> time to look into it deeper (maybe there /was/ an issue with my
>>>>> query. :) I'd prefer that to be taken care of before an M6
>>>>> release, at least. I'll see if I can look into it today and file
>>>>> an issue, if appropriate.
>>>>>
>>>>> Robert
>>>>
>>>> Hi Robert,
>>>>
>>>> could you try your query with the trunk build of the Modeler? I
>>>> just applied the last patch by Olga that fixes a few error
>>>> reporting issues. To get a detailed message you need to roll the
>>>> mouse over the line number on the left (this is a bit unobvious,
>>>> the plan is to replace it with a red circle, Eclipse style).
>>>>
>>>> Andrus
>>>>
>>>
>>>
>>
>
Re: How manay milestones before 3.0 final?
Posted by Andrus Adamchik <an...@objectstyle.org>.
Ah sorry. I was looking at the red underline to detect errors. Error
status on the left was indeed stuck. I just committed the last patch
that shows eclipsy red squiggle on the left, which makes it more
obvious. Olga is looking to fix this and other error message reset
problems that we found.
Andrus
On Apr 10, 2009, at 7:29 AM, Robert Zeigler wrote:
> Ok, I've cleaned out the cayenne portion of my maven repo, and
> verified that the modeler version running is the version from source
> (and it's the current trunk source).
> And I'm still having issues with EJBQLQuery text entry choking on
> very simple queries that "should work".
> For one, there seems to be a case-sensitivity issue.
> select ...
> will complain about wanting a SELECT (or a variety of other tokens)
> at column 0. If I change select to SELECT, that goes away, but
> instead, the query:
> SELECT p.title FROM Protocol AS p
> (alternatively: SELECT p.title FROM Protocol p)
>
> Then it complains: "Encountered " "Protocol"" at line 1, column 16.
> Was expecting ","... "."... "FROM"... "."...
>
> I should note that the problem occurs when trying to save or
> validate the project.
>
> Robert
>
> On Apr 3, 2009, at 4/39:41 AM , Robert Zeigler wrote:
>
>> Tried a mvn clean; mvn install before posting.
>> But it's still possible that I was picking up an older build; I'll
>> clean out the 3.0 branch of my local repo to be sure.
>>
>> Robert
>>
>> On Apr 3, 2009, at 4/34:50 AM , Andrus Adamchik wrote:
>>
>>> Hmm... works for me. Can you make sure you have the latest clean
>>> build, as some parser classes were regenerated, so "mvn clean" is
>>> needed.
>>>
>>> Andrus
>>>
>>>
>>> On Apr 3, 2009, at 12:36 PM, Robert Zeigler wrote:
>>>
>>>> Still having issues.
>>>>
>>>> Even with a very basic query:
>>>> select pr from ProtocolRun pr
>>>>
>>>> I get the following message:
>>>> "Encountered " "pr"" at line 1, column 35
>>>> Was expecting one of:
>>>> ","...
>>>> "ORDER"...
>>>> "WHERE"...
>>>> "GROUP"...
>>>> "HAVING"...
>>>> "LEFT"...
>>>> "INNER"...
>>>> "JOIN"...
>>>>
>>>>
>>>> Robert
>>>>
>>>> On Apr 3, 2009, at 4/31:41 AM , Andrus Adamchik wrote:
>>>>
>>>>>
>>>>> On Mar 30, 2009, at 8:01 PM, Robert Zeigler wrote:
>>>>>
>>>>>> The EJBQLQuery pane in the modeler appears to need some work,
>>>>>> as well; I haven't played with it extensively, but I put
>>>>>> entered a valid query and was informed by the modeler that the
>>>>>> query was invalid (I use the exact same query in my application
>>>>>> with no issues)... haven't filed an issue for this yet as I
>>>>>> haven't had time to look into it deeper (maybe there /was/ an
>>>>>> issue with my query. :) I'd prefer that to be taken care of
>>>>>> before an M6 release, at least. I'll see if I can look into it
>>>>>> today and file an issue, if appropriate.
>>>>>>
>>>>>> Robert
>>>>>
>>>>> Hi Robert,
>>>>>
>>>>> could you try your query with the trunk build of the Modeler? I
>>>>> just applied the last patch by Olga that fixes a few error
>>>>> reporting issues. To get a detailed message you need to roll the
>>>>> mouse over the line number on the left (this is a bit unobvious,
>>>>> the plan is to replace it with a red circle, Eclipse style).
>>>>>
>>>>> Andrus
>>>>>
>>>>
>>>>
>>>
>>
>
>
Re: How manay milestones before 3.0 final?
Posted by Robert Zeigler <ro...@gmail.com>.
Ok, I've cleaned out the cayenne portion of my maven repo, and
verified that the modeler version running is the version from source
(and it's the current trunk source).
And I'm still having issues with EJBQLQuery text entry choking on
very simple queries that "should work".
For one, there seems to be a case-sensitivity issue.
select ...
will complain about wanting a SELECT (or a variety of other tokens) at
column 0. If I change select to SELECT, that goes away, but instead,
the query:
SELECT p.title FROM Protocol AS p
(alternatively: SELECT p.title FROM Protocol p)
Then it complains: "Encountered " "Protocol"" at line 1, column 16.
Was expecting ","... "."... "FROM"... "."...
I should note that the problem occurs when trying to save or validate
the project.
Robert
On Apr 3, 2009, at 4/39:41 AM , Robert Zeigler wrote:
> Tried a mvn clean; mvn install before posting.
> But it's still possible that I was picking up an older build; I'll
> clean out the 3.0 branch of my local repo to be sure.
>
> Robert
>
> On Apr 3, 2009, at 4/34:50 AM , Andrus Adamchik wrote:
>
>> Hmm... works for me. Can you make sure you have the latest clean
>> build, as some parser classes were regenerated, so "mvn clean" is
>> needed.
>>
>> Andrus
>>
>>
>> On Apr 3, 2009, at 12:36 PM, Robert Zeigler wrote:
>>
>>> Still having issues.
>>>
>>> Even with a very basic query:
>>> select pr from ProtocolRun pr
>>>
>>> I get the following message:
>>> "Encountered " "pr"" at line 1, column 35
>>> Was expecting one of:
>>> ","...
>>> "ORDER"...
>>> "WHERE"...
>>> "GROUP"...
>>> "HAVING"...
>>> "LEFT"...
>>> "INNER"...
>>> "JOIN"...
>>>
>>>
>>> Robert
>>>
>>> On Apr 3, 2009, at 4/31:41 AM , Andrus Adamchik wrote:
>>>
>>>>
>>>> On Mar 30, 2009, at 8:01 PM, Robert Zeigler wrote:
>>>>
>>>>> The EJBQLQuery pane in the modeler appears to need some work, as
>>>>> well; I haven't played with it extensively, but I put entered a
>>>>> valid query and was informed by the modeler that the query was
>>>>> invalid (I use the exact same query in my application with no
>>>>> issues)... haven't filed an issue for this yet as I haven't had
>>>>> time to look into it deeper (maybe there /was/ an issue with my
>>>>> query. :) I'd prefer that to be taken care of before an M6
>>>>> release, at least. I'll see if I can look into it today and file
>>>>> an issue, if appropriate.
>>>>>
>>>>> Robert
>>>>
>>>> Hi Robert,
>>>>
>>>> could you try your query with the trunk build of the Modeler? I
>>>> just applied the last patch by Olga that fixes a few error
>>>> reporting issues. To get a detailed message you need to roll the
>>>> mouse over the line number on the left (this is a bit unobvious,
>>>> the plan is to replace it with a red circle, Eclipse style).
>>>>
>>>> Andrus
>>>>
>>>
>>>
>>
>
Re: How manay milestones before 3.0 final?
Posted by Robert Zeigler <ro...@gmail.com>.
Tried a mvn clean; mvn install before posting.
But it's still possible that I was picking up an older build; I'll
clean out the 3.0 branch of my local repo to be sure.
Robert
On Apr 3, 2009, at 4/34:50 AM , Andrus Adamchik wrote:
> Hmm... works for me. Can you make sure you have the latest clean
> build, as some parser classes were regenerated, so "mvn clean" is
> needed.
>
> Andrus
>
>
> On Apr 3, 2009, at 12:36 PM, Robert Zeigler wrote:
>
>> Still having issues.
>>
>> Even with a very basic query:
>> select pr from ProtocolRun pr
>>
>> I get the following message:
>> "Encountered " "pr"" at line 1, column 35
>> Was expecting one of:
>> ","...
>> "ORDER"...
>> "WHERE"...
>> "GROUP"...
>> "HAVING"...
>> "LEFT"...
>> "INNER"...
>> "JOIN"...
>>
>>
>> Robert
>>
>> On Apr 3, 2009, at 4/31:41 AM , Andrus Adamchik wrote:
>>
>>>
>>> On Mar 30, 2009, at 8:01 PM, Robert Zeigler wrote:
>>>
>>>> The EJBQLQuery pane in the modeler appears to need some work, as
>>>> well; I haven't played with it extensively, but I put entered a
>>>> valid query and was informed by the modeler that the query was
>>>> invalid (I use the exact same query in my application with no
>>>> issues)... haven't filed an issue for this yet as I haven't had
>>>> time to look into it deeper (maybe there /was/ an issue with my
>>>> query. :) I'd prefer that to be taken care of before an M6
>>>> release, at least. I'll see if I can look into it today and file
>>>> an issue, if appropriate.
>>>>
>>>> Robert
>>>
>>> Hi Robert,
>>>
>>> could you try your query with the trunk build of the Modeler? I
>>> just applied the last patch by Olga that fixes a few error
>>> reporting issues. To get a detailed message you need to roll the
>>> mouse over the line number on the left (this is a bit unobvious,
>>> the plan is to replace it with a red circle, Eclipse style).
>>>
>>> Andrus
>>>
>>
>>
>
Re: How manay milestones before 3.0 final?
Posted by Andrus Adamchik <an...@objectstyle.org>.
Hmm... works for me. Can you make sure you have the latest clean
build, as some parser classes were regenerated, so "mvn clean" is
needed.
Andrus
On Apr 3, 2009, at 12:36 PM, Robert Zeigler wrote:
> Still having issues.
>
> Even with a very basic query:
> select pr from ProtocolRun pr
>
> I get the following message:
> "Encountered " "pr"" at line 1, column 35
> Was expecting one of:
> ","...
> "ORDER"...
> "WHERE"...
> "GROUP"...
> "HAVING"...
> "LEFT"...
> "INNER"...
> "JOIN"...
>
>
> Robert
>
> On Apr 3, 2009, at 4/31:41 AM , Andrus Adamchik wrote:
>
>>
>> On Mar 30, 2009, at 8:01 PM, Robert Zeigler wrote:
>>
>>> The EJBQLQuery pane in the modeler appears to need some work, as
>>> well; I haven't played with it extensively, but I put entered a
>>> valid query and was informed by the modeler that the query was
>>> invalid (I use the exact same query in my application with no
>>> issues)... haven't filed an issue for this yet as I haven't had
>>> time to look into it deeper (maybe there /was/ an issue with my
>>> query. :) I'd prefer that to be taken care of before an M6
>>> release, at least. I'll see if I can look into it today and file
>>> an issue, if appropriate.
>>>
>>> Robert
>>
>> Hi Robert,
>>
>> could you try your query with the trunk build of the Modeler? I
>> just applied the last patch by Olga that fixes a few error
>> reporting issues. To get a detailed message you need to roll the
>> mouse over the line number on the left (this is a bit unobvious,
>> the plan is to replace it with a red circle, Eclipse style).
>>
>> Andrus
>>
>
>
Re: How manay milestones before 3.0 final?
Posted by Robert Zeigler <ro...@roxanemy.com>.
Still having issues.
Even with a very basic query:
select pr from ProtocolRun pr
I get the following message:
"Encountered " "pr"" at line 1, column 35
Was expecting one of:
","...
"ORDER"...
"WHERE"...
"GROUP"...
"HAVING"...
"LEFT"...
"INNER"...
"JOIN"...
Robert
On Apr 3, 2009, at 4/31:41 AM , Andrus Adamchik wrote:
>
> On Mar 30, 2009, at 8:01 PM, Robert Zeigler wrote:
>
>> The EJBQLQuery pane in the modeler appears to need some work, as
>> well; I haven't played with it extensively, but I put entered a
>> valid query and was informed by the modeler that the query was
>> invalid (I use the exact same query in my application with no
>> issues)... haven't filed an issue for this yet as I haven't had
>> time to look into it deeper (maybe there /was/ an issue with my
>> query. :) I'd prefer that to be taken care of before an M6
>> release, at least. I'll see if I can look into it today and file an
>> issue, if appropriate.
>>
>> Robert
>
> Hi Robert,
>
> could you try your query with the trunk build of the Modeler? I just
> applied the last patch by Olga that fixes a few error reporting
> issues. To get a detailed message you need to roll the mouse over
> the line number on the left (this is a bit unobvious, the plan is to
> replace it with a red circle, Eclipse style).
>
> Andrus
>
Re: How manay milestones before 3.0 final?
Posted by Andrus Adamchik <an...@objectstyle.org>.
On Mar 30, 2009, at 8:01 PM, Robert Zeigler wrote:
> The EJBQLQuery pane in the modeler appears to need some work, as
> well; I haven't played with it extensively, but I put entered a
> valid query and was informed by the modeler that the query was
> invalid (I use the exact same query in my application with no
> issues)... haven't filed an issue for this yet as I haven't had time
> to look into it deeper (maybe there /was/ an issue with my
> query. :) I'd prefer that to be taken care of before an M6 release,
> at least. I'll see if I can look into it today and file an issue, if
> appropriate.
>
> Robert
Hi Robert,
could you try your query with the trunk build of the Modeler? I just
applied the last patch by Olga that fixes a few error reporting
issues. To get a detailed message you need to roll the mouse over the
line number on the left (this is a bit unobvious, the plan is to
replace it with a red circle, Eclipse style).
Andrus
Re: How manay milestones before 3.0 final?
Posted by Robert Zeigler <ro...@gmail.com>.
The EJBQLQuery pane in the modeler appears to need some work, as well;
I haven't played with it extensively, but I put entered a valid query
and was informed by the modeler that the query was invalid (I use the
exact same query in my application with no issues)... haven't filed an
issue for this yet as I haven't had time to look into it deeper (maybe
there /was/ an issue with my query. :) I'd prefer that to be taken
care of before an M6 release, at least. I'll see if I can look into it
today and file an issue, if appropriate.
Robert
On Mar 30, 2009, at 3/303:57 AM , Andrus Adamchik wrote:
>
> On Mar 30, 2009, at 11:42 AM, Aristedes Maniatis wrote:
>
>>
>> Great. Then the main thing to do in the leadup to M6 is to look at
>> the list of tasks assigned to that milestone [1].
>>
>> Three Andrus, one Kevin and one me. Everyone, please add more tasks
>> you are planning to work on in the next fortnight to M6 or remove
>> anything from M6 which is unlikely to happen. Then we'll have a
>> clear goal.
>
>
> I just edited my issues. I'd like to finish CAY-1193. Olga is
> working on it, it mostly works, but still needs serious polishing.
>
>
>> Are there any show stoppers from Cayenne users which need to be
>> looked at for M6? Should we ask on the user list or will they just
>> tell us we need a graphical UML-like modeler? :-)
>
>
> I think we shouldn't. We don't have resources to react to user
> requests so quickly. Even to many of the valid ones.
>
> Andrus
>
Re: How manay milestones before 3.0 final?
Posted by Andrus Adamchik <an...@objectstyle.org>.
On Mar 30, 2009, at 11:42 AM, Aristedes Maniatis wrote:
>
> Great. Then the main thing to do in the leadup to M6 is to look at
> the list of tasks assigned to that milestone [1].
>
> Three Andrus, one Kevin and one me. Everyone, please add more tasks
> you are planning to work on in the next fortnight to M6 or remove
> anything from M6 which is unlikely to happen. Then we'll have a
> clear goal.
I just edited my issues. I'd like to finish CAY-1193. Olga is working
on it, it mostly works, but still needs serious polishing.
> Are there any show stoppers from Cayenne users which need to be
> looked at for M6? Should we ask on the user list or will they just
> tell us we need a graphical UML-like modeler? :-)
I think we shouldn't. We don't have resources to react to user
requests so quickly. Even to many of the valid ones.
Andrus
Re: How manay milestones before 3.0 final?
Posted by Aristedes Maniatis <ar...@ish.com.au>.
On 30/03/2009, at 7:21 PM, Andrey Razumovsky wrote:
> I would very much like M6 to be released as fast as possible, I
> think enough
> time has passed and work done since M5.
Great. Then the main thing to do in the leadup to M6 is to look at the
list of tasks assigned to that milestone [1].
Three Andrus, one Kevin and one me. Everyone, please add more tasks
you are planning to work on in the next fortnight to M6 or remove
anything from M6 which is unlikely to happen. Then we'll have a clear
goal.
Are there any show stoppers from Cayenne users which need to be looked
at for M6? Should we ask on the user list or will they just tell us we
need a graphical UML-like modeler? :-)
> 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
Sure, but just because we release 3.0 doesn't mean they can't go into
3.1. I think mostly we should be concerned by those things that are
likely to change existing APIs (particularly those in 3.0 that aren't
in 2.x). Are your plans of that nature?
There is always a choice between a feature-based release deadline
(that is, we release when we have implemented certain features) and a
date-based one (we stop on a certain date). At least with the latter,
we don't get feature creep stretching on forever.
Ari
[1] https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310903&fixfor=12313759&resolution=-1
-------------------------->
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
Re: How manay milestones before 3.0 final?
Posted by Andrey Razumovsky <ra...@gmail.com>.
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 <an...@objectstyle.org>
> 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, joseph_schmidt71@yahoo.com 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
>>
>>
>>
>>
>
Re: How manay milestones before 3.0 final?
Posted by Andrus Adamchik <an...@objectstyle.org>.
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, joseph_schmidt71@yahoo.com 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
>
>
>
Re: How manay milestones before 3.0 final?
Posted by Aristedes Maniatis <ar...@ish.com.au>.
On 30/03/2009, at 4:45 AM, joseph_schmidt71@yahoo.com 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