When do I know it's OK to commit my changes for JIRA JDO-146?  Is there some
conventional time period during which I wait to hear about an objection
before committing?

--matthew


Matthew T. Adams
Corporate Technical Advisor & Senior Consultant
Mobile:  +1 253 732 1051
Phone:  +1 206 331 3833
Fax:  +1 815 331 0952
matthew.adams@xcalia.com
P.O. Box 24163
Federal Way, WA  98093
www.xcalia.com <http://www.xcalia.com/>



Xcalia makes implementing SOA easy with agile business intermediation
software that combines heterogeneous data with services to easily develop
and deploy transactional composite applications.  Enterprises can quickly
respond to changing business requirements and dramatically reduce the costs
of data access and service integration.

[ Post a follow-up to this message ]

Hi Matthew,

I'm usually extremely cautious about updates to the api20 project. As
soon as the update is available, implementations tracking the api
won't work any more until they update, which means that e.g. you can't
use the latest JPOX with the latest api.

So I usually give folks a couple of days for api20 changes, and
actively solicit feedback from the JPOX team.

Other projects are not nearly as important in terms of breaking other
things, so a day is fine.

This is just my opinion, though. Any others?

Craig

On Sep 23, 2005, at 10:35 AM, Matthew T. Adams wrote:

When do I know it's OK to commit my changes for JIRA JDO-146?  Is
there some conventional time period during which I wait to hear about
an objection before committing?

--matthew

[ Post a follow-up to this message ]

Hi Craig, Matthew,

> I'm usually extremely cautious about updates to the api20 project. As
> soon as the update is available, implementations tracking the api
> won't work any more until they update, which means that e.g. you can't
> use the latest JPOX with the latest api.

JPOX (since maybe Friday last week) contains the PM/PMF methods
get/setDetachAllOnCommit and consequently you should be ok to commit your
changes. JPOX doesn't currently implement the functionality behind
detach-all-on-commit but this shouldn't hold up the API updates and any unit
test writing for it.


--
Andy

[ Post a follow-up to this message ]