Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorWayne Beaton2017-05-03 03:09:34 +0000
committerWayne Beaton2017-05-03 03:09:34 +0000
commit1a76878c90ad2b199f2287f407242c7533903b63 (patch)
treec993939ead9a4c8a64e5b5fff0db62cb9e85f52e
parent3c61353ff25abb13d588f4518f90d99db22b710f (diff)
downloadorg.eclipse.dash.handbook-1a76878c90ad2b199f2287f407242c7533903b63.tar.gz
org.eclipse.dash.handbook-1a76878c90ad2b199f2287f407242c7533903b63.tar.xz
org.eclipse.dash.handbook-1a76878c90ad2b199f2287f407242c7533903b63.zip
[509610] Add an IP FAQ entry regarding whether or not a respin is needed
-rw-r--r--source/chapters/ip.adoc4
1 files changed, 4 insertions, 0 deletions
diff --git a/source/chapters/ip.adoc b/source/chapters/ip.adoc
index 47857ac..987142c 100644
--- a/source/chapters/ip.adoc
+++ b/source/chapters/ip.adoc
@@ -385,6 +385,10 @@ When should I submit the IP Log for review? ::
The IP Log should be submitted for review by the IP Team two weeks before the planned
end date for a release review or (if code moves are involved) a restructuring review.
Note that the date of your review may be different from the date of the actual release.
+
+We submitted an IP Log for our release, but we've made some changes since then that will end up in the release, should we resubmit the IP Log? ::
+
+The purpose of the IP Log review is to checkpoint the IP Due Diligence Process and ensure that nothing is slipping through the cracks; an IP Log is not intended to be an accurate reflection of exactly what is in any particular release.
Are there other reasons to submit the IP Log for review? ::
Generally no. If the IP Team requires an IP Log review outside of the context of

Back to the top