;Bob") Brodt
>> > >> Senior Software Engineer, JBoss Riftsaw
>> > >> JBoss by Red Hat
>> > >>
>> > >> - Original Message -
>> > >>> tshivaraj
>> > >>>
>> > >>&g
id not help to find a preferred slot, we
> > >>>> should
> > >>>> stick to 7:00 utc tomorrow. I don't have access to a conf hosting
> > >>>> service, so I'd prefer skype. Please send me your skype name so that
> > >>>>
>>>> I
> >>>> can add you to the call. Mine is tvanlessen. If you can easily host
> >>>> such a conference, please let me know.
> >>>>
> >>>> Cheers, Tammo
> >>>>
> >>>&
On Tue, Mar 22, 2011 at 11:27 PM, Tammo van Lessen wrote:
> Hi guys,
>
> - JPA Refactoring
> - Status (Jeff): needs some final polishing, some tests need to be
> fixed in mvn build, then it can be committed to trunk. It supports both,
> Hibernate and OpenJPA via JPA 2.0
>
small correction here
;> RegardsJeff
>>>>>
>>>>> On Wed, Mar 16, 2011 at 12:23 AM, Tammo van Lessen
>>>>> wrote:
>>>>> Hi guys,
>>>>>
>>>>> sorry for the delay. Getting a working internet connection took
>>>>> l
etail yet, right?
> > >> RegardsJeff
> > >>
> > >> On Wed, Mar 16, 2011 at 12:23 AM, Tammo van Lessen
> > >> wrote:
> > >> Hi guys,
> > >>
> > >> sorry for the delay. Getting a working internet connection took
> &
move is not yet fully survived ;)
> >
> > To give more notice, I propose to schedule the call for next Tuesday,
> > March 22, 7:00 UTC. An intermediary agenda can be found at
> >
> > ODE Roadmap Call <
> https://docs.google.com/present/edit?id=0Ac2PXMTvfhyeZHEzMmp3
Mine is nickmalthus
Sent from Yahoo! Mail on Android
t;> RegardsJeff
> >>
> >> On Wed, Mar 16, 2011 at 12:23 AM, Tammo van Lessen
> >> wrote:
> >> Hi guys,
> >>
> >> sorry for the delay. Getting a working internet connection took
> >> longer
> >> than expected, also the mo
survived ;)
>>
>> To give more notice, I propose to schedule the call for next Tuesday,
>> March 22, 7:00 UTC. An intermediary agenda can be found at
>>
>> ODE Roadmap
>> Call <https://docs.google.com/present/edit?id=0Ac2PXMTvfhyeZHEzMmp3Yl8xNDFmZ3d3cmY4NQ&hl=
n Lessen
>>> wrote:
>>> Hi guys,
>>>
>>> sorry for the delay. Getting a working internet connection took longer
>>> than expected, also the move is not yet fully survived ;)
>>>
>>> To give more notice, I propose to schedule the cal
urvived ;)
>>
>> To give more notice, I propose to schedule the call for next Tuesday,
>> March 22, 7:00 UTC. An intermediary agenda can be found at
>>
>> ODE Roadmap Call
>> <https://docs.google.com/present/edit?id=0Ac2PXMTvfhyeZHEzMmp3Yl8xNDFmZ3d3cmY4NQ
gt;
> sorry for the delay. Getting a working internet connection took longer
> than expected, also the move is not yet fully survived ;)
>
> To give more notice, I propose to schedule the call for next Tuesday,
> March 22, 7:00 UTC. An intermediary agenda can be found at
>
Hi Tammo,
I think you haven't sent out the conf call's detail yet, right?
Regards
Jeff
On Wed, Mar 16, 2011 at 12:23 AM, Tammo van Lessen wrote:
> Hi guys,
>
> sorry for the delay. Getting a working internet connection took longer
> than expected, also the move is not yet fully survived ;)
>
>
Hi Tammo,
On the process of verifying patch of ODE-915 (
https://issues.apache.org/jira/browse/ODE-915), I found that it seems we've
already had binary incompatibility between the ODE-1.3.5 and the ODE-trunk,
so it might worth discussion on the conf call as well.
For people that are interested, h
7:00 UTC is ok for me as well.
--
Regards,
Mateusz Nowakowski
-Original Message-
From: Jeff Yu [mailto:jeff.yuch...@gmail.com]
Sent: Wednesday, March 16, 2011 1:22 AM
To: dev@ode.apache.org
Cc: Tammo van Lessen
Subject: Re: ODE roadmap
Hi Tammo,
I am ok with it.
Regards
Jeff
On Wed
Hi Tammo,
I am ok with it.
Regards
Jeff
On Wed, Mar 16, 2011 at 12:23 AM, Tammo van Lessen wrote:
> Hi guys,
>
> sorry for the delay. Getting a working internet connection took longer
> than expected, also the move is not yet fully survived ;)
>
> To give more notice, I propose to schedule the
Hi Tammo,
I am ok with proposed time.
Thanks
Milinda
On Tue, Mar 15, 2011 at 7:49 PM, Tammo van Lessen wrote:
> Hi,
>
> yes, I know, but since we're that spread across time zones, it is
> difficult to find a date that is convenient for everybody.
>
> An alternative could be 14:00 or 14:00 UTC.
Hi,
yes, I know, but since we're that spread across time zones, it is
difficult to find a date that is convenient for everybody.
An alternative could be 14:00 or 14:00 UTC.
Please find a doodle poll at http://www.doodle.com/6cse53fh9cs2z8c8
Best,
Tammo
On 15.03.2011 14:50, Gary Brown wrote:
Should be ok for me - but no earlier in the day :)
Regards
Gary
On Tue, Mar 15, 2011 at 1:42 PM, Bob Brodt wrote:
> Wow...that's 1:00 AM on a Tuesday morning for me...
> I think I'll wait for the movie ;)
>
> ___
> Robert ("Bob") Brodt
> Senior Software Engine
Wow...that's 1:00 AM on a Tuesday morning for me...
I think I'll wait for the movie ;)
___
Robert ("Bob") Brodt
Senior Software Engineer, JBoss Riftsaw
JBoss by Red Hat
- Original Message -
> Hi guys,
>
> sorry for the delay. Getting a working internet
Hi guys,
sorry for the delay. Getting a working internet connection took longer
than expected, also the move is not yet fully survived ;)
To give more notice, I propose to schedule the call for next Tuesday,
March 22, 7:00 UTC. An intermediary agenda can be found at
https://docs.google.com/prese
Hi Gary, all
agreed, let's cancel the call and find a better date, perhaps Thu 10th
or Fr 11th of March. Lets pin that down once I have reliable internet
access again (mid next week).
@all, please let me know if none of these work for you or if you
strongly prefer one.
Thanks,
Tammo
On 26.02.
Works for me.
Shivaraj
On Sat, Feb 26, 2011 at 8:05 AM, Jeff Yu wrote:
> I am available.
>
> Regards
> Jeff
>
> On Fri, Feb 25, 2011 at 11:38 PM, Tammo van Lessen >wrote:
>
> > Hi guys,
> >
> > sorry for the delay. Looks like finding a perfect date is quite
> > difficult since our timezone di
Hi Tammo
I could probably make it, but I think it may be better to give more notice,
to ensure as many people can attend.
So would suggest moving the meeting to the following week, after your move?
The time is fine for me, but I would not be able to do Monday or Tuesday
next week.
Regards
Gary
I am available.
Regards
Jeff
On Fri, Feb 25, 2011 at 11:38 PM, Tammo van Lessen wrote:
> Hi guys,
>
> sorry for the delay. Looks like finding a perfect date is quite
> difficult since our timezone distribution could not be better ;)
>
> I hope I resolve the timezone names properly, so here is ou
Hi guys,
sorry for the delay. Looks like finding a perfect date is quite
difficult since our timezone distribution could not be better ;)
I hope I resolve the timezone names properly, so here is our current
situation ;)
http://www.timeanddate.com/worldclock/meetingtime.html?day=25&month=2&year=2
I would like to join, GMT -8 Timezone.
Thanks
Veresh
On 02/08/2011 06:17 AM, Tammo van Lessen wrote:
Hi devs,
a new year, a new release, time to discuss ODE's roadmap again.
There are a couple of issues on my list that I'd like to discuss with you.
1) Status of JPA refactoring
2) Evolveable
I would be interested too - timezone GMT.
In terms of additional topics, would be interested in the buildr vs maven
decision - whether there will be a focus on one in the future, or whether
both have to be maintained.
Regards
Gary
On Thu, Feb 17, 2011 at 2:49 PM, Bob Brodt wrote:
> Hi Tammo,
Hi Tammo,
Have you decided on a date/time for this discussion? I'd like to listen in on
the call. I'm in Colorado, UTC-7 timezone, but WFH and my schedule is very
flexible ;)
Thanks!
___
Robert ("Bob") Brodt
Senior Software Engineer, JBoss Riftsaw
JBoss by R
On 02/11/2011 06:18 AM, Jeff Yu wrote:
Hi Kane,
We would be definitely interested in your JPA 2.0 work, which version of ODE
are you based on? could you please put it somewhere first (preferably on
github), so that we can look into and discuss more to see how to make it
working well with our ODE
Hi Kane,
We would be definitely interested in your JPA 2.0 work, which version of ODE
are you based on? could you please put it somewhere first (preferably on
github), so that we can look into and discuss more to see how to make it
working well with our ODE codebase (may be better to integrate wit
On 02/10/2011 09:59 PM, Kurt Westerfeld wrote:
>> Besides that I'm currently still working on a much better OSGi
>> integration (e.g. using a real service for ODE that in turn configures
>> the Axis2 ManagedService at startup).
>
> If you haven't already, you should try out ODE on Servicemix 4.3
> Besides that I'm currently still working on a much better OSGi
> integration (e.g. using a real service for ODE that in turn configures
> the Axis2 ManagedService at startup).
If you haven't already, you should try out ODE on Servicemix 4.3.X, which is
completely OSGi and has a great integrat
On 02/08/2011 03:17 PM, Tammo van Lessen wrote:
Hi devs,
a new year, a new release, time to discuss ODE's roadmap again.
There are a couple of issues on my list that I'd like to discuss with you.
1) Status of JPA refactoring
2) Evolveable OModel and runtime model
3) Backports from experimental
I would like to join the meeting as well if possible.
I'm GMT+1.
--
Regards,
Mateusz Nowakowski
-Original Message-
From: Paul Brown [mailto:paulrbr...@gmail.com]
Sent: Wednesday, February 09, 2011 7:10 AM
To: dev@ode.apache.org
Subject: Re: ODE roadmap
I'll try to join de
I'll try to join depending on when you guys put it on the calendar.
On Feb 8, 2011, at 5:18 PM, Jeff Yu wrote:
> HI Tammo,
>
> I'd like to join in this meeting, +1 for a skype call. I am in GMT+11
> (Sydney) timezone. I am available at 9:00am - 9:00pm (Sydney time).
>
> Regards
> Jeff
>
> On
+1
I'll also join. I'm in GMT+5.30 timezone.
Thanks
Milinda
On Tue, Feb 8, 2011 at 7:47 PM, Tammo van Lessen wrote:
> Hi devs,
>
> a new year, a new release, time to discuss ODE's roadmap again.
>
> There are a couple of issues on my list that I'd like to discuss with you.
>
> 1) Status of JPA
Please include me too. GMT+5:30 (IST) timezone.
Thanks,
Shivaraj
On Tue, Feb 8, 2011 at 8:18 PM, Jeff Yu wrote:
> HI Tammo,
>
> I'd like to join in this meeting, +1 for a skype call. I am in GMT+11
> (Sydney) timezone. I am available at 9:00am - 9:00pm (Sydney time).
>
> Regards
> Jeff
>
> On
HI Tammo,
I'd like to join in this meeting, +1 for a skype call. I am in GMT+11
(Sydney) timezone. I am available at 9:00am - 9:00pm (Sydney time).
Regards
Jeff
On Wed, Feb 9, 2011 at 1:17 AM, Tammo van Lessen wrote:
> Hi devs,
>
> a new year, a new release, time to discuss ODE's roadmap again.
Hi devs,
a new year, a new release, time to discuss ODE's roadmap again.
There are a couple of issues on my list that I'd like to discuss with you.
1) Status of JPA refactoring
2) Evolveable OModel and runtime model
3) Backports from experimental
4) Community & Eco system
What do you think of h
On Sat, Jun 19, 2010 at 3:56 AM, David Carver wrote:
> Just some thoughts on this thread.
>
> 1. Any 1.4 or 1.3.x release should always be API compatible. So we should
> never break public API here.
>
> 2. I would prefer that any schema changes and any serialization of classes
> also remain bin
Just some thoughts on this thread.
1. Any 1.4 or 1.3.x release should always be API compatible. So we
should never break public API here.
2. I would prefer that any schema changes and any serialization of
classes also remain binary compatible. Again, avoids migration and
upgrade issues.
We can edit this with our plans:
http://ode.apache.org/roadmap.html
We can sort by priority, but not plan for particular release.
On Fri, Jun 18, 2010 at 11:53 AM, Jeff Yu wrote:
> one clarification, when I say plan, it is not a detailed requirement etc,
> just some features that we thought woul
On Fri, Jun 18, 2010 at 11:48 AM, Jeff Yu wrote:
> I was thinking about 2 months release with 2 weeks forking (code freeze with
> that branch). ;-)
OK, it's fine.
>
> Regards
> jeff
>
> On Fri, Jun 18, 2010 at 6:54 PM, Rafal Rusin wrote:
>
>> I would prefer to release 1.3.5 and then 1.4.0.
>> I
one clarification, when I say plan, it is not a detailed requirement etc,
just some features that we thought would be better to be included,
but if it turns out can not be completed in the given time frame, we can
delay it to next release for sure.
Regards
Jeff
On Fri, Jun 18, 2010 at 7:51 PM, Je
I think this can come from our long-term goal, we can have this sort of
discussion just after the release.
IMHO, Certainly, for the bug fix release, we can just grab what we have and
deliver.
but for others, it is better that we have some plans.
Regards
Jeff
On Fri, Jun 18, 2010 at 7:40 PM, Rafal
I was thinking about 2 months release with 2 weeks forking (code freeze with
that branch). ;-)
Regards
jeff
On Fri, Jun 18, 2010 at 6:54 PM, Rafal Rusin wrote:
> I would prefer to release 1.3.5 and then 1.4.0.
> I'm fine with 1.3.5 as soon as there are running maven axis2-war tests
> in hudson.
And one thing. I don't like planning for particular features to
include in some release. I prefer to grab what we have in regular
period of time and make release from it (and move outstanding issues
into next release). This is how it works.
On Fri, Jun 18, 2010 at 11:35 AM, Rafal Rusin wrote:
> O
this sounds good to me.
Regards
Jeff
On Fri, Jun 18, 2010 at 7:35 PM, Rafal Rusin wrote:
> >
> > The question would be if we need a 1.3.5 or if we can go directly for a
> 1.4.
>
> We can now stay with 1.3.5. If JPA refatoring will be committed before
> 15-th July, then we'll mark it 1.4.
> Othe
On Fri, Jun 18, 2010 at 11:19 AM, Tammo van Lessen wrote:
> Hi,
>
> I'm fine with that, too. We should also define a long-term road map.
>
> Regarding the versions, especially when we release more often (which I
> would really appreciate), we should better communicate the philosophy
> behind versi
Hi,
I'm fine with that, too. We should also define a long-term road map.
Regarding the versions, especially when we release more often (which I
would really appreciate), we should better communicate the philosophy
behind versioning. 1.3.x should never require migration efforts and
should be consi
I would prefer to release 1.3.5 and then 1.4.0.
I'm fine with 1.3.5 as soon as there are running maven axis2-war tests
in hudson.
And I agree - we should release regularly. Something like every 2
months with 1 month forking period (beta release).
So we can plan 1.3.5 fork on 15-th July and release
Hi team,
Since we've released the 1.3.4, I am thinking about our roadmap for the next
release.
Firstly, I'd think that it is better that we have a release plan like 1
release in 2 months at least, could be just a bug fix release, or a feature
enhancement, as long as we have something to deliver,
54 matches
Mail list logo
