Community
Participate
Working Groups
see news://news.eclipse.org:119/h97isn$6g2$1@build.eclipse.org We should identify all existing timeouts in CDO and add API for easy user-/admin-configuration as well as documentation which timeouts exist and what they influence.
Ok, I'll start: - protocol timeout, default: 10s can be set using ((org.eclipse.emf.cdo.net4j.CDOSession)session).options().getProtocol().setTimeout(t); - monitor timeout, default: 10s (this is one of those I am currently struggling with)
Ok, I have done a deeper research "monitor timeout" for me is really: - commit timeout, default: 10s can be set using ((org.eclipse.emf.cdo.net4j.CDOSession)session).options().setCommitTimeout(t);
Rebasing all outstanding enhancements requests to version 4.0
Moving all open enhancement requests to 4.1
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Moving all outstanding enhancements to 4.3
Moving all open enhancement requests to 4.4
Moving all open bugzillas to 4.5.
Moving all unaddressed bugzillas to 4.6.
Moving all open bugs to 4.7
Moving all unresolved issues to version 4.8-
Moving all unresolved issues to version 4.9
Moving to 4.13.