Re: Do we want to release the 0.9.1 now?
Hi, Jakob and Yan, I have back-ported SAMZA-608, SAMZA-658, and SAMZA-616 to 0.9.1 branch. And the 0.9.1 release will now include bugfixes: SAMZA-608 SAMZA-616 SAMZA-658 SAMZA-662 I think that would be a good minimum list of bugfixes. I have attached the back-ported fixes to all JIRAs mentioned above and if you can give a +1 to move forward quickly with 0.9.1 release, that would be great! Thanks a lot! -Yi On Thu, May 21, 2015 at 4:21 PM, Yi Pan nickpa...@gmail.com wrote: Hi, Jakob, Thanks a lot for the thorough check-through. I agree w/ your point that those bug fixes are important and should be back ported. @Yan and others, what are your opinions? I will back port SAMZA-608 now. On the branch/tag methodology, I would prefer to make the change in the next release in 0.10, since it is more for a long-term strategy. -Yi On Thu, May 21, 2015 at 2:44 PM, Jakob Homan jgho...@gmail.com wrote: Currently we have individual branches for each of the point releases (0.8.1, 0.9.0, 0.9.1, etc). It may be better to have a single 0.9 branch and then demarcate the actual releases through git tags. This way the branch becomes more stable over time as bug fixes are applied (in a magical world where bug fixes themselves can never introduce new bugs. Also unicorns). I mentioned in the JIRA, but it'd be really good to commit bug fixes back to their original branches so that users can download and deploy the branch quickly (without worrying about trying to generate their own patches) and to ease point releases. This would avoid the following type of analysis: Since 0.9.0, the following JIRAs have been applied to trunk: * db2d93e - (HEAD - master, origin/master, origin/HEAD) SAMZA-643: Improve error messages fro null stream in OutgoingMessageEnvelop (6 days ago) Gustavo Anatoly * a94e1ed - SAMZA-537: added RocksDB TTL support (7 days ago) Naveen Somasundaram * e801ab2 - SAMZA-662: fixed auto-created changelog stream does not have enough partitions when container number 1 (8 days ago) Guozhang Wang * 4323003 - SAMZA-658: fix cached store iterator remove() function (2 weeks ago) Guozhang Wang * f0809a5 - SAMZA-657: add checkstyle to build script (2 weeks ago) Guozhang Wang * bb8a78a - SAMZA-557: Reuse local state in SamzaContainer on clean shutdown (2 weeks ago) Navina Ramesh * 9f30ef1 - SAMZA-647 add batch get API to KV-store (2 weeks ago) Mohamed Mahmoud * fdb90e7 - SAMZA-660: Added default serdes for changelog streams (3 weeks ago) Tommy Becker * 23fb2e1 - SAMZA-465: Use coordinator stream and eliminate CheckpointManager (3 weeks ago) Naveen Somasundaram * c37d752 - SAMZA-433: Rename task to container in AM and container (4 weeks ago) Benjamin Fradet * 88a844b - SAMZA-655: Add environment variable configuration rewriter. (4 weeks ago) Dan Harvey * 5a035b8 - Update committer list (5 weeks ago) Yi Pan (Data Infrastructure) * a09b1ff - SAMZA-646: Remove support for JDK6 (5 weeks ago) Jakob Homan * ffa84c0 - SAMZA-608; don't hange on serde errors in system consumers (5 weeks ago) Yi Pan * 3eb15a0 - SAMZA-629: add instructions for upgrading websites when releasing new version (6 weeks ago) Yan Fang * 6946f78 - SAMZA-540: Expose checkpointed offset in OffsetManager (6 weeks ago) Renato Marroquín Mogrovejo * 9427c9e - SAMZA-634; stop job coordinator when process job exits (6 weeks ago) Tommy Becker * 81f54a2 - SAMZA-616; make shutdown hook wait for container to finish (6 weeks ago) Tommy Becker * edc2c78 - SAMZA-636; add a uuid serde (6 weeks ago) Mohamed Mahmoud (El-Geish) * b276afe - SAMZA-624: Remove Travis integration (6 weeks ago) Jakob Homan * 457a524 - SAMZA-638: Add Stream Name to SystemConsumersException Message (6 weeks ago) Navina Ramesh * 76e151c - SAMZA-633; expose configuration to Kafka's encoder and decoder (7 weeks ago) Dan Harvey * cde495e - SAMZA-627: add 0.9.0 release to Archive category (7 weeks ago) Yan Fang * 95b6afc - update download page for 0.9.0 (7 weeks ago) Yan Fang * faf93ff - SAMZA-621; fix zopkio test package path for 0.10.0 (8 weeks ago) Chris Riccomini * 8aeec8d - SAMZA-620; torture test checker should start from oldest offset (8 weeks ago) Chris Riccomini * d20ae5c - SAMZA-367: add Timer to the docs (8 weeks ago) Yan Fang * 44d07f6 - SAMZA-613: update 0.9.0 release version. bump up to 0.10.0-SNAPSHOT (8 weeks ago) Yan Fang Of these, SAMZA-658 (fix cached store iterator remove() function), SAMZA-608 (don't hange on serde errors in system consumers) and SAMZA-616 (make shutdown hook wait for container to finish) are all bug fixes that I think should be eligible for a 0.9.1 point release. Should we work on backporting those patches, or do people not think it's worth the effort for these bugs?' -Jakob On 21 May 2015 at 14:27, Yan Fang yanfang...@gmail.com wrote: Sounds good! Thanks, Fang, Yan yanfang...@gmail.com On Thu, May 21, 2015 at 2:24 PM, Yi Pan nickpa...@gmail.com wrote:
Re: Do we want to release the 0.9.1 now?
Agreed to back port those bug fixes. On the branch/tag methodology, I think we can start in next release because we already have opened the 0.9.1 branch and applied patch to it. Thanks, Fang, Yan yanfang...@gmail.com On Thu, May 21, 2015 at 4:21 PM, Yi Pan nickpa...@gmail.com wrote: Hi, Jakob, Thanks a lot for the thorough check-through. I agree w/ your point that those bug fixes are important and should be back ported. @Yan and others, what are your opinions? I will back port SAMZA-608 now. On the branch/tag methodology, I would prefer to make the change in the next release in 0.10, since it is more for a long-term strategy. -Yi On Thu, May 21, 2015 at 2:44 PM, Jakob Homan jgho...@gmail.com wrote: Currently we have individual branches for each of the point releases (0.8.1, 0.9.0, 0.9.1, etc). It may be better to have a single 0.9 branch and then demarcate the actual releases through git tags. This way the branch becomes more stable over time as bug fixes are applied (in a magical world where bug fixes themselves can never introduce new bugs. Also unicorns). I mentioned in the JIRA, but it'd be really good to commit bug fixes back to their original branches so that users can download and deploy the branch quickly (without worrying about trying to generate their own patches) and to ease point releases. This would avoid the following type of analysis: Since 0.9.0, the following JIRAs have been applied to trunk: * db2d93e - (HEAD - master, origin/master, origin/HEAD) SAMZA-643: Improve error messages fro null stream in OutgoingMessageEnvelop (6 days ago) Gustavo Anatoly * a94e1ed - SAMZA-537: added RocksDB TTL support (7 days ago) Naveen Somasundaram * e801ab2 - SAMZA-662: fixed auto-created changelog stream does not have enough partitions when container number 1 (8 days ago) Guozhang Wang * 4323003 - SAMZA-658: fix cached store iterator remove() function (2 weeks ago) Guozhang Wang * f0809a5 - SAMZA-657: add checkstyle to build script (2 weeks ago) Guozhang Wang * bb8a78a - SAMZA-557: Reuse local state in SamzaContainer on clean shutdown (2 weeks ago) Navina Ramesh * 9f30ef1 - SAMZA-647 add batch get API to KV-store (2 weeks ago) Mohamed Mahmoud * fdb90e7 - SAMZA-660: Added default serdes for changelog streams (3 weeks ago) Tommy Becker * 23fb2e1 - SAMZA-465: Use coordinator stream and eliminate CheckpointManager (3 weeks ago) Naveen Somasundaram * c37d752 - SAMZA-433: Rename task to container in AM and container (4 weeks ago) Benjamin Fradet * 88a844b - SAMZA-655: Add environment variable configuration rewriter. (4 weeks ago) Dan Harvey * 5a035b8 - Update committer list (5 weeks ago) Yi Pan (Data Infrastructure) * a09b1ff - SAMZA-646: Remove support for JDK6 (5 weeks ago) Jakob Homan * ffa84c0 - SAMZA-608; don't hange on serde errors in system consumers (5 weeks ago) Yi Pan * 3eb15a0 - SAMZA-629: add instructions for upgrading websites when releasing new version (6 weeks ago) Yan Fang * 6946f78 - SAMZA-540: Expose checkpointed offset in OffsetManager (6 weeks ago) Renato Marroquín Mogrovejo * 9427c9e - SAMZA-634; stop job coordinator when process job exits (6 weeks ago) Tommy Becker * 81f54a2 - SAMZA-616; make shutdown hook wait for container to finish (6 weeks ago) Tommy Becker * edc2c78 - SAMZA-636; add a uuid serde (6 weeks ago) Mohamed Mahmoud (El-Geish) * b276afe - SAMZA-624: Remove Travis integration (6 weeks ago) Jakob Homan * 457a524 - SAMZA-638: Add Stream Name to SystemConsumersException Message (6 weeks ago) Navina Ramesh * 76e151c - SAMZA-633; expose configuration to Kafka's encoder and decoder (7 weeks ago) Dan Harvey * cde495e - SAMZA-627: add 0.9.0 release to Archive category (7 weeks ago) Yan Fang * 95b6afc - update download page for 0.9.0 (7 weeks ago) Yan Fang * faf93ff - SAMZA-621; fix zopkio test package path for 0.10.0 (8 weeks ago) Chris Riccomini * 8aeec8d - SAMZA-620; torture test checker should start from oldest offset (8 weeks ago) Chris Riccomini * d20ae5c - SAMZA-367: add Timer to the docs (8 weeks ago) Yan Fang * 44d07f6 - SAMZA-613: update 0.9.0 release version. bump up to 0.10.0-SNAPSHOT (8 weeks ago) Yan Fang Of these, SAMZA-658 (fix cached store iterator remove() function), SAMZA-608 (don't hange on serde errors in system consumers) and SAMZA-616 (make shutdown hook wait for container to finish) are all bug fixes that I think should be eligible for a 0.9.1 point release. Should we work on backporting those patches, or do people not think it's worth the effort for these bugs?' -Jakob On 21 May 2015 at 14:27, Yan Fang yanfang...@gmail.com wrote: Sounds good! Thanks, Fang, Yan yanfang...@gmail.com On Thu, May 21, 2015 at 2:24 PM, Yi Pan nickpa...@gmail.com wrote: Hi, Yan, I am voting to start it now. Guozhang has already signed up to follow the release
Re: Do we want to release the 0.9.1 now?
Currently we have individual branches for each of the point releases (0.8.1, 0.9.0, 0.9.1, etc). It may be better to have a single 0.9 branch and then demarcate the actual releases through git tags. This way the branch becomes more stable over time as bug fixes are applied (in a magical world where bug fixes themselves can never introduce new bugs. Also unicorns). I mentioned in the JIRA, but it'd be really good to commit bug fixes back to their original branches so that users can download and deploy the branch quickly (without worrying about trying to generate their own patches) and to ease point releases. This would avoid the following type of analysis: Since 0.9.0, the following JIRAs have been applied to trunk: * db2d93e - (HEAD - master, origin/master, origin/HEAD) SAMZA-643: Improve error messages fro null stream in OutgoingMessageEnvelop (6 days ago) Gustavo Anatoly * a94e1ed - SAMZA-537: added RocksDB TTL support (7 days ago) Naveen Somasundaram * e801ab2 - SAMZA-662: fixed auto-created changelog stream does not have enough partitions when container number 1 (8 days ago) Guozhang Wang * 4323003 - SAMZA-658: fix cached store iterator remove() function (2 weeks ago) Guozhang Wang * f0809a5 - SAMZA-657: add checkstyle to build script (2 weeks ago) Guozhang Wang * bb8a78a - SAMZA-557: Reuse local state in SamzaContainer on clean shutdown (2 weeks ago) Navina Ramesh * 9f30ef1 - SAMZA-647 add batch get API to KV-store (2 weeks ago) Mohamed Mahmoud * fdb90e7 - SAMZA-660: Added default serdes for changelog streams (3 weeks ago) Tommy Becker * 23fb2e1 - SAMZA-465: Use coordinator stream and eliminate CheckpointManager (3 weeks ago) Naveen Somasundaram * c37d752 - SAMZA-433: Rename task to container in AM and container (4 weeks ago) Benjamin Fradet * 88a844b - SAMZA-655: Add environment variable configuration rewriter. (4 weeks ago) Dan Harvey * 5a035b8 - Update committer list (5 weeks ago) Yi Pan (Data Infrastructure) * a09b1ff - SAMZA-646: Remove support for JDK6 (5 weeks ago) Jakob Homan * ffa84c0 - SAMZA-608; don't hange on serde errors in system consumers (5 weeks ago) Yi Pan * 3eb15a0 - SAMZA-629: add instructions for upgrading websites when releasing new version (6 weeks ago) Yan Fang * 6946f78 - SAMZA-540: Expose checkpointed offset in OffsetManager (6 weeks ago) Renato Marroquín Mogrovejo * 9427c9e - SAMZA-634; stop job coordinator when process job exits (6 weeks ago) Tommy Becker * 81f54a2 - SAMZA-616; make shutdown hook wait for container to finish (6 weeks ago) Tommy Becker * edc2c78 - SAMZA-636; add a uuid serde (6 weeks ago) Mohamed Mahmoud (El-Geish) * b276afe - SAMZA-624: Remove Travis integration (6 weeks ago) Jakob Homan * 457a524 - SAMZA-638: Add Stream Name to SystemConsumersException Message (6 weeks ago) Navina Ramesh * 76e151c - SAMZA-633; expose configuration to Kafka's encoder and decoder (7 weeks ago) Dan Harvey * cde495e - SAMZA-627: add 0.9.0 release to Archive category (7 weeks ago) Yan Fang * 95b6afc - update download page for 0.9.0 (7 weeks ago) Yan Fang * faf93ff - SAMZA-621; fix zopkio test package path for 0.10.0 (8 weeks ago) Chris Riccomini * 8aeec8d - SAMZA-620; torture test checker should start from oldest offset (8 weeks ago) Chris Riccomini * d20ae5c - SAMZA-367: add Timer to the docs (8 weeks ago) Yan Fang * 44d07f6 - SAMZA-613: update 0.9.0 release version. bump up to 0.10.0-SNAPSHOT (8 weeks ago) Yan Fang Of these, SAMZA-658 (fix cached store iterator remove() function), SAMZA-608 (don't hange on serde errors in system consumers) and SAMZA-616 (make shutdown hook wait for container to finish) are all bug fixes that I think should be eligible for a 0.9.1 point release. Should we work on backporting those patches, or do people not think it's worth the effort for these bugs?' -Jakob On 21 May 2015 at 14:27, Yan Fang yanfang...@gmail.com wrote: Sounds good! Thanks, Fang, Yan yanfang...@gmail.com On Thu, May 21, 2015 at 2:24 PM, Yi Pan nickpa...@gmail.com wrote: Hi, Yan, I am voting to start it now. Guozhang has already signed up to follow the release process that Chris wrote up. There will be an announcement soon. Thanks! -Yi On Thu, May 21, 2015 at 2:21 PM, Yan Fang yanfang...@gmail.com wrote: Hi guys, Just ask, are there any other bugs that we want to back port to 0.9.1 besides SAMZA-662 https://issues.apache.org/jira/browse/SAMZA-662 ? If no, I think we can prepare the 0.9.1 release and ask for the vote. Cheers, Fang, Yan yanfang...@gmail.com
Re: Do we want to release the 0.9.1 now?
Hi, Yan, I am voting to start it now. Guozhang has already signed up to follow the release process that Chris wrote up. There will be an announcement soon. Thanks! -Yi On Thu, May 21, 2015 at 2:21 PM, Yan Fang yanfang...@gmail.com wrote: Hi guys, Just ask, are there any other bugs that we want to back port to 0.9.1 besides SAMZA-662 https://issues.apache.org/jira/browse/SAMZA-662 ? If no, I think we can prepare the 0.9.1 release and ask for the vote. Cheers, Fang, Yan yanfang...@gmail.com
Re: Do we want to release the 0.9.1 now?
Sounds good! Thanks, Fang, Yan yanfang...@gmail.com On Thu, May 21, 2015 at 2:24 PM, Yi Pan nickpa...@gmail.com wrote: Hi, Yan, I am voting to start it now. Guozhang has already signed up to follow the release process that Chris wrote up. There will be an announcement soon. Thanks! -Yi On Thu, May 21, 2015 at 2:21 PM, Yan Fang yanfang...@gmail.com wrote: Hi guys, Just ask, are there any other bugs that we want to back port to 0.9.1 besides SAMZA-662 https://issues.apache.org/jira/browse/SAMZA-662 ? If no, I think we can prepare the 0.9.1 release and ask for the vote. Cheers, Fang, Yan yanfang...@gmail.com
Re: Do we want to release the 0.9.1 now?
Hi, Jakob, Thanks a lot for the thorough check-through. I agree w/ your point that those bug fixes are important and should be back ported. @Yan and others, what are your opinions? I will back port SAMZA-608 now. On the branch/tag methodology, I would prefer to make the change in the next release in 0.10, since it is more for a long-term strategy. -Yi On Thu, May 21, 2015 at 2:44 PM, Jakob Homan jgho...@gmail.com wrote: Currently we have individual branches for each of the point releases (0.8.1, 0.9.0, 0.9.1, etc). It may be better to have a single 0.9 branch and then demarcate the actual releases through git tags. This way the branch becomes more stable over time as bug fixes are applied (in a magical world where bug fixes themselves can never introduce new bugs. Also unicorns). I mentioned in the JIRA, but it'd be really good to commit bug fixes back to their original branches so that users can download and deploy the branch quickly (without worrying about trying to generate their own patches) and to ease point releases. This would avoid the following type of analysis: Since 0.9.0, the following JIRAs have been applied to trunk: * db2d93e - (HEAD - master, origin/master, origin/HEAD) SAMZA-643: Improve error messages fro null stream in OutgoingMessageEnvelop (6 days ago) Gustavo Anatoly * a94e1ed - SAMZA-537: added RocksDB TTL support (7 days ago) Naveen Somasundaram * e801ab2 - SAMZA-662: fixed auto-created changelog stream does not have enough partitions when container number 1 (8 days ago) Guozhang Wang * 4323003 - SAMZA-658: fix cached store iterator remove() function (2 weeks ago) Guozhang Wang * f0809a5 - SAMZA-657: add checkstyle to build script (2 weeks ago) Guozhang Wang * bb8a78a - SAMZA-557: Reuse local state in SamzaContainer on clean shutdown (2 weeks ago) Navina Ramesh * 9f30ef1 - SAMZA-647 add batch get API to KV-store (2 weeks ago) Mohamed Mahmoud * fdb90e7 - SAMZA-660: Added default serdes for changelog streams (3 weeks ago) Tommy Becker * 23fb2e1 - SAMZA-465: Use coordinator stream and eliminate CheckpointManager (3 weeks ago) Naveen Somasundaram * c37d752 - SAMZA-433: Rename task to container in AM and container (4 weeks ago) Benjamin Fradet * 88a844b - SAMZA-655: Add environment variable configuration rewriter. (4 weeks ago) Dan Harvey * 5a035b8 - Update committer list (5 weeks ago) Yi Pan (Data Infrastructure) * a09b1ff - SAMZA-646: Remove support for JDK6 (5 weeks ago) Jakob Homan * ffa84c0 - SAMZA-608; don't hange on serde errors in system consumers (5 weeks ago) Yi Pan * 3eb15a0 - SAMZA-629: add instructions for upgrading websites when releasing new version (6 weeks ago) Yan Fang * 6946f78 - SAMZA-540: Expose checkpointed offset in OffsetManager (6 weeks ago) Renato Marroquín Mogrovejo * 9427c9e - SAMZA-634; stop job coordinator when process job exits (6 weeks ago) Tommy Becker * 81f54a2 - SAMZA-616; make shutdown hook wait for container to finish (6 weeks ago) Tommy Becker * edc2c78 - SAMZA-636; add a uuid serde (6 weeks ago) Mohamed Mahmoud (El-Geish) * b276afe - SAMZA-624: Remove Travis integration (6 weeks ago) Jakob Homan * 457a524 - SAMZA-638: Add Stream Name to SystemConsumersException Message (6 weeks ago) Navina Ramesh * 76e151c - SAMZA-633; expose configuration to Kafka's encoder and decoder (7 weeks ago) Dan Harvey * cde495e - SAMZA-627: add 0.9.0 release to Archive category (7 weeks ago) Yan Fang * 95b6afc - update download page for 0.9.0 (7 weeks ago) Yan Fang * faf93ff - SAMZA-621; fix zopkio test package path for 0.10.0 (8 weeks ago) Chris Riccomini * 8aeec8d - SAMZA-620; torture test checker should start from oldest offset (8 weeks ago) Chris Riccomini * d20ae5c - SAMZA-367: add Timer to the docs (8 weeks ago) Yan Fang * 44d07f6 - SAMZA-613: update 0.9.0 release version. bump up to 0.10.0-SNAPSHOT (8 weeks ago) Yan Fang Of these, SAMZA-658 (fix cached store iterator remove() function), SAMZA-608 (don't hange on serde errors in system consumers) and SAMZA-616 (make shutdown hook wait for container to finish) are all bug fixes that I think should be eligible for a 0.9.1 point release. Should we work on backporting those patches, or do people not think it's worth the effort for these bugs?' -Jakob On 21 May 2015 at 14:27, Yan Fang yanfang...@gmail.com wrote: Sounds good! Thanks, Fang, Yan yanfang...@gmail.com On Thu, May 21, 2015 at 2:24 PM, Yi Pan nickpa...@gmail.com wrote: Hi, Yan, I am voting to start it now. Guozhang has already signed up to follow the release process that Chris wrote up. There will be an announcement soon. Thanks! -Yi On Thu, May 21, 2015 at 2:21 PM, Yan Fang yanfang...@gmail.com wrote: Hi guys, Just ask, are there any other bugs that we want to back port to 0.9.1 besides SAMZA-662 https://issues.apache.org/jira/browse/SAMZA-662 ? If no, I think we can prepare the 0.9.1 release and ask for the
