I can provide a quick fix on 4.0 branch. For 4.0 branch, what is the process to commit a fix? Submit a patch for Joe to commit, or I can directly commit?
Thanks -min On 4/18/13 11:08 AM, "Chip Childers" <chip.child...@sungard.com> wrote: >On Thu, Apr 18, 2013 at 11:07:18AM -0700, Alena Prokharchyk wrote: >> On 4/18/13 11:02 AM, "Chip Childers" <chip.child...@sungard.com> wrote: >> >> >On Thu, Apr 18, 2013 at 10:57:51AM -0700, Alena Prokharchyk wrote: >> >> On 4/18/13 10:48 AM, "Chip Childers" <chip.child...@sungard.com> >>wrote: >> >> >> >> >On Thu, Apr 18, 2013 at 10:46:38AM -0700, Alena Prokharchyk wrote: >> >> >> I would probably leave it for 4.2.0. And update the release notes >>for >> >> >>4.0 >> >> >> >> >> >> Chip, what do you think? >> >> > >> >> >Doesn't 4.1 actually have the right code in it already? >> >> > >> >> >I think Joe is asking about the 4.0 branch, since he's about to cut >>the >> >> >second RC for that code line. >> >> >> >> >> >> 4.1 does have correct code. Chip, would you advise to patch 4.0? It >> >>would >> >> require java code changes - fixing annotations in the APIs. Then we >>have >> >> to generate new xml/html api docs. >> >> >> >> -Alena. >> > >> >Joe's the RM for the 4.0.2 release. I think he's asking about (1) >> >impact, (2) risk and (3) how quick the fix will be. We're about to >> >start another round of voting for 4.0.2, and generating new API docs >> >will be part of that release process anyway. The question is really >> >intended to get the code clean so that the (hopefully) last 4.0.x >> >release has correct docs in it. >> > >> >> >> There is a minimal impact - only api docs will get affected, and the fix >> should be relatively quick as all we have to do is to fix >>@Implementation >> parameter in 3 java classes. >> >> > >I *think* joe would love a patch for the 4.0 branch for this!
