You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Andrus Adamchik <an...@objectstyle.org> on 2014/12/01 12:06:25 UTC
preparing for 4.0.M2
Just did some preliminary work to prepare for M2 release. Fixed a few minor issues with the tests and licensing, wrote some "what's new" docs. Here are the test results (Java 7, OS X) :
rat: PASSED
hsql: PASSED
h2: PASSED
derby: PASSED
mysql 5.0 PASSED
mysql 5.6 PASSED
sqlserver FAILURES: Failures: 18, Errors: 3, Skipped: 0
postgresql: PASSED
oracle 11: ?
This is comparable with 3.1 results [1] (need to look at sqlserver failures though). There's one new issue [2] that will need to be fixed before we start the vote - the new DbImporter work resulted in slowing down DbMerger, so that PostgreSQL tests now take an hour, MySQL tests are much slower than before, and I ran out of patience with Oracle tests after ~2 hours and canceled the build.
We are getting close though. I think I'll actually create a "stable" branch for 4.0.M2, as new changes will keep coming in and we want the release to happen :)
Andrus
[1] http://markmail.org/message/zlasxkq6tpzhydev
[2] https://issues.apache.org/jira/browse/CAY-1976
Re: preparing for 4.0.M2
Posted by Andrus Adamchik <an...@objectstyle.org>.
> On Dec 2, 2014, at 2:12 PM, Andrus Adamchik <an...@objectstyle.org> wrote:
>
>>
>> I think our previous naming regime would have this branch called STABLE-4.0 if we are ready to now make trunk/head available for new work that will not land into 4.0.
>
> I didn't give much thought to the branch naming in this instance, as I am planning to merge and delete this branch after the release (leaving the tag around of course). So it is a short-lived thing.
BTW, after realizing that we still need to do some work to stabilize the newest features, I killed that branch. So all the M2 code still goes to master until further notice.
Andrus
Re: preparing for 4.0.M2
Posted by Michael Gentry <mg...@masslight.net>.
The ones I have only return the sum/avg/count/min/max for a given query,
not the original rows, too.
On Wed, Dec 3, 2014 at 2:07 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
> Perhaps something more integrated. I.e. an aggregate expression will be
> part of a query, with an option to return the main object together with an
> aggregate (more generally - with an option to customize the SELECT clause).
> E.g. an equivalent of the following EJBQL which already works:
>
> "SELECT a, count(a.paintings) FROM a"
>
> Andrus
>
>
> > On Dec 2, 2014, at 7:28 PM, Michael Gentry <mg...@masslight.net>
> wrote:
> >
> > Will the AggregateUtils thing I did be helpful?
> >
> >
> > On Tue, Dec 2, 2014 at 6:12 AM, Andrus Adamchik <an...@objectstyle.org>
> > wrote:
> >
> >>
> >>> On Dec 2, 2014, at 1:51 PM, Aristedes Maniatis <ar...@maniatis.org>
> wrote:
> >>>
> >>> On 2/12/2014 7:53pm, Andrus Adamchik wrote:
> >>>>
> >>>>> On Dec 1, 2014, at 2:06 PM, Andrus Adamchik <an...@objectstyle.org>
> >> wrote:
> >>>>>
> >>>>> I think I'll actually create a "stable" branch for 4.0.M2, as new
> >> changes will keep coming in and we want the release to happen
> >>>>
> >>>> Which I just did:
> >> https://github.com/apache/cayenne/tree/4.0.M2_prerelease
> >>>
> >>> Cool. There is a lot of great work in there.
> >>
> >> Yep. My app code looks so much cleaner after I migrated it to the new
> >> APIs. And while still raw, the new cdbimport rules.
> >>
> >>> I think our previous naming regime would have this branch called
> >> STABLE-4.0 if we are ready to now make trunk/head available for new work
> >> that will not land into 4.0.
> >>
> >> I didn't give much thought to the branch naming in this instance, as I
> am
> >> planning to merge and delete this branch after the release (leaving the
> tag
> >> around of course). So it is a short-lived thing.
> >>
> >>> If this really is the end of all new features, then perhaps the next
> >> release will be 4.0-beta1?
> >>
> >> There's more query API work planned. We need to align ProcedureQuery and
> >> NamedQuery, and create a fluent thing for non-selecting SQLTemplates.
> >> Though these can be done pretty quickly.
> >>
> >> A bigger project is to bring all EJBQLQuery functionality into
> >> ObjectSelect - multi-result selects, aggregate queries, etc. This is
> more
> >> challenging. Whether this stuff should be 4.0 or say 4.1 is debatable. I
> >> feel there's lots of benefit in a quick completion of 4.0. There are
> users
> >> who are only allowed to use "GA" tagged dependencies in their work. And
> by
> >> the time we get a "full solution", a few years may pass and it won't be
> as
> >> exciting by then :) So I am +1 on the Beta idea.
> >>
> >> Andrus
>
>
Re: preparing for 4.0.M2
Posted by Andrus Adamchik <an...@objectstyle.org>.
Perhaps something more integrated. I.e. an aggregate expression will be part of a query, with an option to return the main object together with an aggregate (more generally - with an option to customize the SELECT clause). E.g. an equivalent of the following EJBQL which already works:
"SELECT a, count(a.paintings) FROM a"
Andrus
> On Dec 2, 2014, at 7:28 PM, Michael Gentry <mg...@masslight.net> wrote:
>
> Will the AggregateUtils thing I did be helpful?
>
>
> On Tue, Dec 2, 2014 at 6:12 AM, Andrus Adamchik <an...@objectstyle.org>
> wrote:
>
>>
>>> On Dec 2, 2014, at 1:51 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>>>
>>> On 2/12/2014 7:53pm, Andrus Adamchik wrote:
>>>>
>>>>> On Dec 1, 2014, at 2:06 PM, Andrus Adamchik <an...@objectstyle.org>
>> wrote:
>>>>>
>>>>> I think I'll actually create a "stable" branch for 4.0.M2, as new
>> changes will keep coming in and we want the release to happen
>>>>
>>>> Which I just did:
>> https://github.com/apache/cayenne/tree/4.0.M2_prerelease
>>>
>>> Cool. There is a lot of great work in there.
>>
>> Yep. My app code looks so much cleaner after I migrated it to the new
>> APIs. And while still raw, the new cdbimport rules.
>>
>>> I think our previous naming regime would have this branch called
>> STABLE-4.0 if we are ready to now make trunk/head available for new work
>> that will not land into 4.0.
>>
>> I didn't give much thought to the branch naming in this instance, as I am
>> planning to merge and delete this branch after the release (leaving the tag
>> around of course). So it is a short-lived thing.
>>
>>> If this really is the end of all new features, then perhaps the next
>> release will be 4.0-beta1?
>>
>> There's more query API work planned. We need to align ProcedureQuery and
>> NamedQuery, and create a fluent thing for non-selecting SQLTemplates.
>> Though these can be done pretty quickly.
>>
>> A bigger project is to bring all EJBQLQuery functionality into
>> ObjectSelect - multi-result selects, aggregate queries, etc. This is more
>> challenging. Whether this stuff should be 4.0 or say 4.1 is debatable. I
>> feel there's lots of benefit in a quick completion of 4.0. There are users
>> who are only allowed to use "GA" tagged dependencies in their work. And by
>> the time we get a "full solution", a few years may pass and it won't be as
>> exciting by then :) So I am +1 on the Beta idea.
>>
>> Andrus
Re: preparing for 4.0.M2
Posted by Michael Gentry <mg...@masslight.net>.
Will the AggregateUtils thing I did be helpful?
On Tue, Dec 2, 2014 at 6:12 AM, Andrus Adamchik <an...@objectstyle.org>
wrote:
>
> > On Dec 2, 2014, at 1:51 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> >
> > On 2/12/2014 7:53pm, Andrus Adamchik wrote:
> >>
> >>> On Dec 1, 2014, at 2:06 PM, Andrus Adamchik <an...@objectstyle.org>
> wrote:
> >>>
> >>> I think I'll actually create a "stable" branch for 4.0.M2, as new
> changes will keep coming in and we want the release to happen
> >>
> >> Which I just did:
> https://github.com/apache/cayenne/tree/4.0.M2_prerelease
> >
> > Cool. There is a lot of great work in there.
>
> Yep. My app code looks so much cleaner after I migrated it to the new
> APIs. And while still raw, the new cdbimport rules.
>
> > I think our previous naming regime would have this branch called
> STABLE-4.0 if we are ready to now make trunk/head available for new work
> that will not land into 4.0.
>
> I didn't give much thought to the branch naming in this instance, as I am
> planning to merge and delete this branch after the release (leaving the tag
> around of course). So it is a short-lived thing.
>
> > If this really is the end of all new features, then perhaps the next
> release will be 4.0-beta1?
>
> There's more query API work planned. We need to align ProcedureQuery and
> NamedQuery, and create a fluent thing for non-selecting SQLTemplates.
> Though these can be done pretty quickly.
>
> A bigger project is to bring all EJBQLQuery functionality into
> ObjectSelect - multi-result selects, aggregate queries, etc. This is more
> challenging. Whether this stuff should be 4.0 or say 4.1 is debatable. I
> feel there's lots of benefit in a quick completion of 4.0. There are users
> who are only allowed to use "GA" tagged dependencies in their work. And by
> the time we get a "full solution", a few years may pass and it won't be as
> exciting by then :) So I am +1 on the Beta idea.
>
> Andrus
Re: preparing for 4.0.M2
Posted by Andrus Adamchik <an...@objectstyle.org>.
> On Dec 2, 2014, at 1:51 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
>
> On 2/12/2014 7:53pm, Andrus Adamchik wrote:
>>
>>> On Dec 1, 2014, at 2:06 PM, Andrus Adamchik <an...@objectstyle.org> wrote:
>>>
>>> I think I'll actually create a "stable" branch for 4.0.M2, as new changes will keep coming in and we want the release to happen
>>
>> Which I just did: https://github.com/apache/cayenne/tree/4.0.M2_prerelease
>
> Cool. There is a lot of great work in there.
Yep. My app code looks so much cleaner after I migrated it to the new APIs. And while still raw, the new cdbimport rules.
> I think our previous naming regime would have this branch called STABLE-4.0 if we are ready to now make trunk/head available for new work that will not land into 4.0.
I didn't give much thought to the branch naming in this instance, as I am planning to merge and delete this branch after the release (leaving the tag around of course). So it is a short-lived thing.
> If this really is the end of all new features, then perhaps the next release will be 4.0-beta1?
There's more query API work planned. We need to align ProcedureQuery and NamedQuery, and create a fluent thing for non-selecting SQLTemplates. Though these can be done pretty quickly.
A bigger project is to bring all EJBQLQuery functionality into ObjectSelect - multi-result selects, aggregate queries, etc. This is more challenging. Whether this stuff should be 4.0 or say 4.1 is debatable. I feel there's lots of benefit in a quick completion of 4.0. There are users who are only allowed to use "GA" tagged dependencies in their work. And by the time we get a "full solution", a few years may pass and it won't be as exciting by then :) So I am +1 on the Beta idea.
Andrus
Re: preparing for 4.0.M2
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 2/12/2014 7:53pm, Andrus Adamchik wrote:
>
>> On Dec 1, 2014, at 2:06 PM, Andrus Adamchik <an...@objectstyle.org> wrote:
>>
>> I think I'll actually create a "stable" branch for 4.0.M2, as new changes will keep coming in and we want the release to happen
>
> Which I just did: https://github.com/apache/cayenne/tree/4.0.M2_prerelease
Cool. There is a lot of great work in there. I think our previous naming regime would have this branch called STABLE-4.0 if we are ready to now make trunk/head available for new work that will not land into 4.0.
If this really is the end of all new features, then perhaps the next release will be 4.0-beta1?
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: preparing for 4.0.M2
Posted by Andrus Adamchik <an...@objectstyle.org>.
> On Dec 1, 2014, at 2:06 PM, Andrus Adamchik <an...@objectstyle.org> wrote:
>
> I think I'll actually create a "stable" branch for 4.0.M2, as new changes will keep coming in and we want the release to happen
Which I just did: https://github.com/apache/cayenne/tree/4.0.M2_prerelease