Hello Jukka, Thanks for the clarification. I will in the future always mark the issues for the proper patch release then, and brush up on svn merge, because I'm used to doing merges by hand :)
For JCR-2622 yes I wrote my question too soon, I noticed afterwards that there was no fix required. Best regards, Serge Huber. On 6 janv. 2011, at 16:55, Jukka Zitting wrote: > Hi, > > On Thu, Jan 6, 2011 at 12:04 PM, Serge Huber <[email protected]> wrote: >> First of all thanks for porting the ISDESCENDANT node to the 2.2 branch. > > No problem. To answer your previous question about it, anyone can > merge fixes back to maintenance branches (just remember to use "svn > merge" so we have proper merge tracking records in place) but it's the > responsibility of the release manager to take care of any pending > merges before cutting the release candidate. > > I already have the merging process pretty streamlined, so usually it's > easiest to simply tag a Jira issue for inclusion in a patch release, > and I'll take care of the merging as a part of the release preparation > phase. > >> I noticed you didn't include 2622 ? Do you think it should not be included >> for 2.2.1 ? > > I looked at the issue, but agreed with Fabrizio's conclusion that we > actually don't need to fix that. > > BR, > > Jukka Zitting
