You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by Clinton Begin <cl...@gmail.com> on 2006/11/02 18:50:01 UTC
[NOTICE] Intending to release 2.2.1
Hi everyone,
I would like to release iBATIS 2.2.1 by the end of the weekend if possible.
It's a pretty significant release, probably more than just a
X.X.1release....we could call it
2.3 if you think that would be more appropriate.
The changes so far are:
o DEPRECATED All PaginatedList related features due to misuse, minimal
applicability and inflexibility
o DEPRECATED DAO Framework -- Removed from primary distribution, available
as a separate download
o Removed DAO framework from Subversion source tree (tagged before removal)
o Changed deployment file naming convention, dropped "DBL" and lowercased
all
o Merged common and sqlmap jar files (no more DAO means there's no point in
keeping commons separate)
o Implemented transaction level PreparedStatement caching
o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies
Are there any bugs etc. that should make it into the next release?
Cheers,
Clinton
Re: [NOTICE] Intending to release 2.2.1
Posted by Carlos Cajina <ce...@hotmail.com>.
Great news!
I agree with the 2.3 version label considering the changes that we should expect for this release: (JAR) packaging, API...
Good luck!
Regards,
Carlos
----- Original Message -----
From: Clinton Begin
To: user-java@ibatis.apache.org ; dev@ibatis.apache.org
Sent: Thursday, November 02, 2006 11:50 AM
Subject: [NOTICE] Intending to release 2.2.1
Hi everyone,
I would like to release iBATIS 2.2.1 by the end of the weekend if possible.
It's a pretty significant release, probably more than just a X.X.1 release....we could call it 2.3 if you think that would be more appropriate.
The changes so far are:
o DEPRECATED All PaginatedList related features due to misuse, minimal applicability and inflexibility
o DEPRECATED DAO Framework -- Removed from primary distribution, available as a separate download
o Removed DAO framework from Subversion source tree (tagged before removal)
o Changed deployment file naming convention, dropped "DBL" and lowercased all
o Merged common and sqlmap jar files (no more DAO means there's no point in keeping commons separate)
o Implemented transaction level PreparedStatement caching
o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies
Are there any bugs etc. that should make it into the next release?
Cheers,
Clinton
Re: [NOTICE] Intending to release 2.2.1
Posted by Clinton Begin <cl...@gmail.com>.
>> interface immutability principle,
Principles are not made to be followed blindly. If they were, progress
would be ground to a halt. How else are we to learn from our mistakes but
to change what we've made?
Regardless...deprecation doesn't stop you from using anything. It just
says: "we officially recommend you don't."
Clinton
On 11/7/06, navrsale <na...@yahoo.ca> wrote:
>
>
> Although it seems straightforward and logical decision, I don't think it
> is a
> good idea, primarily because of
> interface immutability principle, which have been proven as beneficial on
> many large scale projects. Once it is
> published it is published, that's it (for example, in servlet specs there
> are still some things dating back from 1998, and yes, I had to follow
> these
> same old APIs on the latest platforms as recently as last year, for the
> reasons which are hard to comprehand ;)
>
>
>
> Clinton Begin wrote:
> >
> > Actually I've heard the opposite opinion. Having the DAO included in
> the
> > same download was confusing to new users.
> >
> > A separate download (made really clear) will work well.
> >
> > Cheers,
> > Clinton
> >
> > On 11/3/06, Brandon Goodin <br...@gmail.com> wrote:
> >>
> >> I just posted this issue that i'd like to fix for this release. It is a
> >> simple fix. But, i wanted to get some feedback as to where we should
> >> place
> >> it.
> >>
> >> https://issues.apache.org/jira/browse/IBATIS-363
> >>
> >>
> >> Also, I think we need to still make the DAO available on the site for
> >> download. Except we need to mark it as deprecated and unsupported. We
> >> should
> >> also provide upgrade instructions to users if we aren't already going
> to
> >> do
> >> so. I can see where this move will be very confusing to some. There are
> >> some
> >> people who are still using the DAO including our example app.
> >>
> >> Brandon
> >>
> >>
> >> On 11/2/06, Clinton Begin <cl...@gmail.com> wrote:
> >> >
> >> > Hi everyone,
> >> >
> >> > I would like to release iBATIS 2.2.1 by the end of the weekend if
> >> > possible.
> >> >
> >> > It's a pretty significant release, probably more than just a
> >> X.X.1release....we could call it
> >> > 2.3 if you think that would be more appropriate.
> >> >
> >> > The changes so far are:
> >> >
> >> > o DEPRECATED All PaginatedList related features due to misuse,
> minimal
> >> > applicability and inflexibility
> >> > o DEPRECATED DAO Framework -- Removed from primary distribution,
> >> > available as a separate download
> >> > o Removed DAO framework from Subversion source tree (tagged before
> >> > removal)
> >> > o Changed deployment file naming convention, dropped "DBL" and
> >> > lowercased all
> >> > o Merged common and sqlmap jar files (no more DAO means there's no
> >> > point in keeping commons separate)
> >> > o Implemented transaction level PreparedStatement caching
> >> > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value
> specified
> >> > o Fixed IBATIS-353 - Probe exception when using inheritance
> >> hierarchies
> >> >
> >> > Are there any bugs etc. that should make it into the next release?
> >> >
> >> > Cheers,
> >> >
> >> > Clinton
> >> >
> >>
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/-NOTICE--Intending-to-release-2.2.1-tf2562384.html#a7233226
> Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
>
>
Re: [NOTICE] Intending to release 2.2.1
Posted by navrsale <na...@yahoo.ca>.
Although it seems straightforward and logical decision, I don't think it is a
good idea, primarily because of
interface immutability principle, which have been proven as beneficial on
many large scale projects. Once it is
published it is published, that's it (for example, in servlet specs there
are still some things dating back from 1998, and yes, I had to follow these
same old APIs on the latest platforms as recently as last year, for the
reasons which are hard to comprehand ;)
Clinton Begin wrote:
>
> Actually I've heard the opposite opinion. Having the DAO included in the
> same download was confusing to new users.
>
> A separate download (made really clear) will work well.
>
> Cheers,
> Clinton
>
> On 11/3/06, Brandon Goodin <br...@gmail.com> wrote:
>>
>> I just posted this issue that i'd like to fix for this release. It is a
>> simple fix. But, i wanted to get some feedback as to where we should
>> place
>> it.
>>
>> https://issues.apache.org/jira/browse/IBATIS-363
>>
>>
>> Also, I think we need to still make the DAO available on the site for
>> download. Except we need to mark it as deprecated and unsupported. We
>> should
>> also provide upgrade instructions to users if we aren't already going to
>> do
>> so. I can see where this move will be very confusing to some. There are
>> some
>> people who are still using the DAO including our example app.
>>
>> Brandon
>>
>>
>> On 11/2/06, Clinton Begin <cl...@gmail.com> wrote:
>> >
>> > Hi everyone,
>> >
>> > I would like to release iBATIS 2.2.1 by the end of the weekend if
>> > possible.
>> >
>> > It's a pretty significant release, probably more than just a
>> X.X.1release....we could call it
>> > 2.3 if you think that would be more appropriate.
>> >
>> > The changes so far are:
>> >
>> > o DEPRECATED All PaginatedList related features due to misuse, minimal
>> > applicability and inflexibility
>> > o DEPRECATED DAO Framework -- Removed from primary distribution,
>> > available as a separate download
>> > o Removed DAO framework from Subversion source tree (tagged before
>> > removal)
>> > o Changed deployment file naming convention, dropped "DBL" and
>> > lowercased all
>> > o Merged common and sqlmap jar files (no more DAO means there's no
>> > point in keeping commons separate)
>> > o Implemented transaction level PreparedStatement caching
>> > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
>> > o Fixed IBATIS-353 - Probe exception when using inheritance
>> hierarchies
>> >
>> > Are there any bugs etc. that should make it into the next release?
>> >
>> > Cheers,
>> >
>> > Clinton
>> >
>>
>>
>
>
--
View this message in context: http://www.nabble.com/-NOTICE--Intending-to-release-2.2.1-tf2562384.html#a7233226
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
Re: [NOTICE] Intending to release 2.2.1
Posted by Clinton Begin <cl...@gmail.com>.
I love it when we say the same thing. :-)
I think everyone will like the new packaging, and my ultimate goal is to
make everything more clear on the website.
BTW: Continuum ROCKS and I'd like to set it up to deploy the site
automatically with SVN commits (in addition to building the iBATIS source),
but unfortunately the WestHost RH Linux build sucks bigtime and I keep
getting core dumps when Java calls svn. It works fine on my home machine.
It will happen. I'll ping some Apache folks about using Apache infra for
this....it would be more secure too.
Cheers,
Clinton
On 11/3/06, Brandon Goodin <br...@gmail.com> wrote:
>
> I'm sorry, i misread your first email... we are saying the same thing.
>
> On 11/3/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> >
> > Actually I've heard the opposite opinion. Having the DAO included in
> > the same download was confusing to new users.
> >
> > A separate download (made really clear) will work well.
> >
> > Cheers,
> > Clinton
> >
> > On 11/3/06, Brandon Goodin <br...@gmail.com> wrote:
> > >
> > > I just posted this issue that i'd like to fix for this release. It is
> > > a simple fix. But, i wanted to get some feedback as to where we should place
> > > it.
> > >
> > > https://issues.apache.org/jira/browse/IBATIS-363
> > >
> > >
> > > Also, I think we need to still make the DAO available on the site for
> > > download. Except we need to mark it as deprecated and unsupported. We should
> > > also provide upgrade instructions to users if we aren't already going to do
> > > so. I can see where this move will be very confusing to some. There are some
> > > people who are still using the DAO including our example app.
> > >
> > > Brandon
> > >
> > >
> > > On 11/2/06, Clinton Begin < clinton.begin@gmail.com> wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > I would like to release iBATIS 2.2.1 by the end of the weekend if
> > > > possible.
> > > >
> > > > It's a pretty significant release, probably more than just a X.X.1release....we could call it
> > > > 2.3 if you think that would be more appropriate.
> > > >
> > > > The changes so far are:
> > > >
> > > > o DEPRECATED All PaginatedList related features due to misuse,
> > > > minimal applicability and inflexibility
> > > > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > > > available as a separate download
> > > > o Removed DAO framework from Subversion source tree (tagged before
> > > > removal)
> > > > o Changed deployment file naming convention, dropped "DBL" and
> > > > lowercased all
> > > > o Merged common and sqlmap jar files (no more DAO means there's no
> > > > point in keeping commons separate)
> > > > o Implemented transaction level PreparedStatement caching
> > > > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value
> > > > specified
> > > > o Fixed IBATIS-353 - Probe exception when using inheritance
> > > > hierarchies
> > > >
> > > > Are there any bugs etc. that should make it into the next release?
> > > >
> > > > Cheers,
> > > >
> > > > Clinton
> > > >
> > >
> > >
> >
>
Re: [NOTICE] Intending to release 2.2.1
Posted by Brandon Goodin <br...@gmail.com>.
I'm sorry, i misread your first email... we are saying the same thing.
On 11/3/06, Clinton Begin <cl...@gmail.com> wrote:
>
> Actually I've heard the opposite opinion. Having the DAO included in the
> same download was confusing to new users.
>
> A separate download (made really clear) will work well.
>
> Cheers,
> Clinton
>
> On 11/3/06, Brandon Goodin <br...@gmail.com> wrote:
> >
> > I just posted this issue that i'd like to fix for this release. It is a
> > simple fix. But, i wanted to get some feedback as to where we should place
> > it.
> >
> > https://issues.apache.org/jira/browse/IBATIS-363
> >
> >
> > Also, I think we need to still make the DAO available on the site for
> > download. Except we need to mark it as deprecated and unsupported. We should
> > also provide upgrade instructions to users if we aren't already going to do
> > so. I can see where this move will be very confusing to some. There are some
> > people who are still using the DAO including our example app.
> >
> > Brandon
> >
> >
> > On 11/2/06, Clinton Begin < clinton.begin@gmail.com> wrote:
> > >
> > > Hi everyone,
> > >
> > > I would like to release iBATIS 2.2.1 by the end of the weekend if
> > > possible.
> > >
> > > It's a pretty significant release, probably more than just a X.X.1release....we could call it
> > > 2.3 if you think that would be more appropriate.
> > >
> > > The changes so far are:
> > >
> > > o DEPRECATED All PaginatedList related features due to misuse,
> > > minimal applicability and inflexibility
> > > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > > available as a separate download
> > > o Removed DAO framework from Subversion source tree (tagged before
> > > removal)
> > > o Changed deployment file naming convention, dropped "DBL" and
> > > lowercased all
> > > o Merged common and sqlmap jar files (no more DAO means there's no
> > > point in keeping commons separate)
> > > o Implemented transaction level PreparedStatement caching
> > > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> > > o Fixed IBATIS-353 - Probe exception when using inheritance
> > > hierarchies
> > >
> > > Are there any bugs etc. that should make it into the next release?
> > >
> > > Cheers,
> > >
> > > Clinton
> > >
> >
> >
>
Re: [NOTICE] Intending to release 2.2.1
Posted by Clinton Begin <cl...@gmail.com>.
Actually I've heard the opposite opinion. Having the DAO included in the
same download was confusing to new users.
A separate download (made really clear) will work well.
Cheers,
Clinton
On 11/3/06, Brandon Goodin <br...@gmail.com> wrote:
>
> I just posted this issue that i'd like to fix for this release. It is a
> simple fix. But, i wanted to get some feedback as to where we should place
> it.
>
> https://issues.apache.org/jira/browse/IBATIS-363
>
>
> Also, I think we need to still make the DAO available on the site for
> download. Except we need to mark it as deprecated and unsupported. We should
> also provide upgrade instructions to users if we aren't already going to do
> so. I can see where this move will be very confusing to some. There are some
> people who are still using the DAO including our example app.
>
> Brandon
>
>
> On 11/2/06, Clinton Begin <cl...@gmail.com> wrote:
> >
> > Hi everyone,
> >
> > I would like to release iBATIS 2.2.1 by the end of the weekend if
> > possible.
> >
> > It's a pretty significant release, probably more than just a X.X.1release....we could call it
> > 2.3 if you think that would be more appropriate.
> >
> > The changes so far are:
> >
> > o DEPRECATED All PaginatedList related features due to misuse, minimal
> > applicability and inflexibility
> > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > available as a separate download
> > o Removed DAO framework from Subversion source tree (tagged before
> > removal)
> > o Changed deployment file naming convention, dropped "DBL" and
> > lowercased all
> > o Merged common and sqlmap jar files (no more DAO means there's no
> > point in keeping commons separate)
> > o Implemented transaction level PreparedStatement caching
> > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> > o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies
> >
> > Are there any bugs etc. that should make it into the next release?
> >
> > Cheers,
> >
> > Clinton
> >
>
>
Re: [NOTICE] Intending to release 2.2.1
Posted by Brandon Goodin <br...@gmail.com>.
that's fine.
On 11/3/06, Clinton Begin <cl...@gmail.com> wrote:
>
>
> >> https://issues.apache.org/jira/browse/IBATIS-363
> <https://issues.apache.org/jira/browse/IBATIS-363>
>
> I had a look and commented on this issue in JIRA. Can I request to move
> forward with 2.3 without this fix? As you will see in my comments...there
> are a couple of issues with changing this behavior.
>
> Would that be okay?
>
> Cheers,
> Clinton
>
>
> On 11/3/06, Brandon Goodin < brandon.goodin@gmail.com> wrote:
> >
> > I just posted this issue that i'd like to fix for this release. It is a
> > simple fix. But, i wanted to get some feedback as to where we should place
> > it.
> >
> > https://issues.apache.org/jira/browse/IBATIS-363
> >
> >
> > Also, I think we need to still make the DAO available on the site for
> > download. Except we need to mark it as deprecated and unsupported. We should
> > also provide upgrade instructions to users if we aren't already going to do
> > so. I can see where this move will be very confusing to some. There are some
> > people who are still using the DAO including our example app.
> >
> > Brandon
> >
> >
> > On 11/2/06, Clinton Begin < clinton.begin@gmail.com> wrote:
> > >
> > > Hi everyone,
> > >
> > > I would like to release iBATIS 2.2.1 by the end of the weekend if
> > > possible.
> > >
> > > It's a pretty significant release, probably more than just a X.X.1release....we could call it
> > > 2.3 if you think that would be more appropriate.
> > >
> > > The changes so far are:
> > >
> > > o DEPRECATED All PaginatedList related features due to misuse,
> > > minimal applicability and inflexibility
> > > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > > available as a separate download
> > > o Removed DAO framework from Subversion source tree (tagged before
> > > removal)
> > > o Changed deployment file naming convention, dropped "DBL" and
> > > lowercased all
> > > o Merged common and sqlmap jar files (no more DAO means there's no
> > > point in keeping commons separate)
> > > o Implemented transaction level PreparedStatement caching
> > > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> > > o Fixed IBATIS-353 - Probe exception when using inheritance
> > > hierarchies
> > >
> > > Are there any bugs etc. that should make it into the next release?
> > >
> > > Cheers,
> > >
> > > Clinton
> > >
> >
> >
>
Re: [NOTICE] Intending to release 2.2.1
Posted by Brandon Goodin <br...@gmail.com>.
I commented on the bug. I can go ahead and mark it deprecated unless you
feel we need to put it in front of the team.
https://issues.apache.org/jira/browse/IBATIS-363
Brandon
On 11/3/06, Clinton Begin <cl...@gmail.com> wrote:
>
>
> >> https://issues.apache.org/jira/browse/IBATIS-363
> <https://issues.apache.org/jira/browse/IBATIS-363>
>
> I had a look and commented on this issue in JIRA. Can I request to move
> forward with 2.3 without this fix? As you will see in my comments...there
> are a couple of issues with changing this behavior.
>
> Would that be okay?
>
> Cheers,
> Clinton
>
>
> On 11/3/06, Brandon Goodin < brandon.goodin@gmail.com> wrote:
> >
> > I just posted this issue that i'd like to fix for this release. It is a
> > simple fix. But, i wanted to get some feedback as to where we should place
> > it.
> >
> > https://issues.apache.org/jira/browse/IBATIS-363
> >
> >
> > Also, I think we need to still make the DAO available on the site for
> > download. Except we need to mark it as deprecated and unsupported. We should
> > also provide upgrade instructions to users if we aren't already going to do
> > so. I can see where this move will be very confusing to some. There are some
> > people who are still using the DAO including our example app.
> >
> > Brandon
> >
> >
> > On 11/2/06, Clinton Begin < clinton.begin@gmail.com> wrote:
> > >
> > > Hi everyone,
> > >
> > > I would like to release iBATIS 2.2.1 by the end of the weekend if
> > > possible.
> > >
> > > It's a pretty significant release, probably more than just a X.X.1release....we could call it
> > > 2.3 if you think that would be more appropriate.
> > >
> > > The changes so far are:
> > >
> > > o DEPRECATED All PaginatedList related features due to misuse,
> > > minimal applicability and inflexibility
> > > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > > available as a separate download
> > > o Removed DAO framework from Subversion source tree (tagged before
> > > removal)
> > > o Changed deployment file naming convention, dropped "DBL" and
> > > lowercased all
> > > o Merged common and sqlmap jar files (no more DAO means there's no
> > > point in keeping commons separate)
> > > o Implemented transaction level PreparedStatement caching
> > > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> > > o Fixed IBATIS-353 - Probe exception when using inheritance
> > > hierarchies
> > >
> > > Are there any bugs etc. that should make it into the next release?
> > >
> > > Cheers,
> > >
> > > Clinton
> > >
> >
> >
>
Re: [NOTICE] Intending to release 2.2.1
Posted by Clinton Begin <cl...@gmail.com>.
>> https://issues.apache.org/jira/browse/IBATIS-363
<https://issues.apache.org/jira/browse/IBATIS-363>
I had a look and commented on this issue in JIRA. Can I request to move
forward with 2.3 without this fix? As you will see in my comments...there
are a couple of issues with changing this behavior.
Would that be okay?
Cheers,
Clinton
On 11/3/06, Brandon Goodin <br...@gmail.com> wrote:
>
> I just posted this issue that i'd like to fix for this release. It is a
> simple fix. But, i wanted to get some feedback as to where we should place
> it.
>
> https://issues.apache.org/jira/browse/IBATIS-363
>
>
> Also, I think we need to still make the DAO available on the site for
> download. Except we need to mark it as deprecated and unsupported. We should
> also provide upgrade instructions to users if we aren't already going to do
> so. I can see where this move will be very confusing to some. There are some
> people who are still using the DAO including our example app.
>
> Brandon
>
>
> On 11/2/06, Clinton Begin < clinton.begin@gmail.com> wrote:
> >
> > Hi everyone,
> >
> > I would like to release iBATIS 2.2.1 by the end of the weekend if
> > possible.
> >
> > It's a pretty significant release, probably more than just a X.X.1release....we could call it
> > 2.3 if you think that would be more appropriate.
> >
> > The changes so far are:
> >
> > o DEPRECATED All PaginatedList related features due to misuse, minimal
> > applicability and inflexibility
> > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > available as a separate download
> > o Removed DAO framework from Subversion source tree (tagged before
> > removal)
> > o Changed deployment file naming convention, dropped "DBL" and
> > lowercased all
> > o Merged common and sqlmap jar files (no more DAO means there's no
> > point in keeping commons separate)
> > o Implemented transaction level PreparedStatement caching
> > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> > o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies
> >
> > Are there any bugs etc. that should make it into the next release?
> >
> > Cheers,
> >
> > Clinton
> >
>
>
Re: [NOTICE] Intending to release 2.2.1
Posted by Brandon Goodin <br...@gmail.com>.
I just posted this issue that i'd like to fix for this release. It is a
simple fix. But, i wanted to get some feedback as to where we should place
it.
https://issues.apache.org/jira/browse/IBATIS-363
Also, I think we need to still make the DAO available on the site for
download. Except we need to mark it as deprecated and unsupported. We should
also provide upgrade instructions to users if we aren't already going to do
so. I can see where this move will be very confusing to some. There are some
people who are still using the DAO including our example app.
Brandon
On 11/2/06, Clinton Begin <cl...@gmail.com> wrote:
>
> Hi everyone,
>
> I would like to release iBATIS 2.2.1 by the end of the weekend if
> possible.
>
> It's a pretty significant release, probably more than just a X.X.1release....we could call it
> 2.3 if you think that would be more appropriate.
>
> The changes so far are:
>
> o DEPRECATED All PaginatedList related features due to misuse, minimal
> applicability and inflexibility
> o DEPRECATED DAO Framework -- Removed from primary distribution,
> available as a separate download
> o Removed DAO framework from Subversion source tree (tagged before
> removal)
> o Changed deployment file naming convention, dropped "DBL" and lowercased
> all
> o Merged common and sqlmap jar files (no more DAO means there's no point
> in keeping commons separate)
> o Implemented transaction level PreparedStatement caching
> o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies
>
> Are there any bugs etc. that should make it into the next release?
>
> Cheers,
>
> Clinton
>