Chris, all, Not sure if there's a 'standard' Apache way to handle release branching? We should define how we'll handle any commit to the release branch in terms of when to merge to master and also what to do with any commits to non-0.7.0 Jiras prior to the release being cut. Otherwise we'll end up with a surprise and much hilarity at some point. :)
Garry -----Original Message----- From: Chris Riccomini [mailto:[email protected]] Sent: 07 April 2014 16:19 To: [email protected] Subject: Samza 0.7.0 Release Branch Hey Guys, I've cut an 0.7.0 release branch starting with commit bd2fb6776ddaf41e3a6b80adab75656505ee72d7 (current master). The branch is called "0.7.0", and can be browsed here: https://git-wip-us.apache.org/repos/asf?p=incubator-samza.git;a=shortlog;h=refs/heads/0.7.0 I'm assuming that github will mirror it shortly, but we'll see. I've also updated the JIRAs tagged with 0.7.0 based on this conversation: http://mail-archives.apache.org/mod_mbox/samza-dev/201403.mbox/%3ccf560494.25b5e%[email protected]%3E These are the JIRAs that were removed from the 0.7.0 release: https://issues.apache.org/jira/browse/SAMZA-123 https://issues.apache.org/jira/browse/SAMZA-122 https://issues.apache.org/jira/browse/SAMZA-84 https://issues.apache.org/jira/browse/SAMZA-14 https://issues.apache.org/jira/browse/SAMZA-79 https://issues.apache.org/jira/browse/SAMZA-89 https://issues.apache.org/jira/browse/SAMZA-107 https://issues.apache.org/jira/browse/SAMZA-221 To see a list of the currently unresolved 0.7.0 JIRAs, go to: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SAMZA%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%200.7.0%20ORDER%20BY%20priority%20DESC If you disagree, and think these were removed in error, please speak up. Cheers, Chris ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4355 / Virus Database: 3722/7301 - Release Date: 04/04/14
