{"thread":{"id":"40254","subject":"Do you plan to release 2.5.2 any time soon?","startedAt":"2015-09-02T22:40:53Z","lastAt":"2015-09-04T07:08:13Z","messageCount":3,"participants":["Johannes Schindelin","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"269245","messageId":"alpine.DEB.1.00.1509030038460.16897@s15462909.onlinehome-server.info","threadId":"40254","inReplyTo":null,"subject":"Do you plan to release 2.5.2 any time soon?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2015-09-02T22:40:53Z","receivedAt":"2015-09-02T22:40:53Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nI have a couple of fixes lined up for bugs in Git for Windows 2.5.1. Do\nyou plan to release 2.5.2 any time soon? If yes, I would hold off,\notherwise I will just do a Git for Windows 2.5.1 (Rel 2).\n\nThanks,\nDscho\n"},{"id":"269350","messageId":"xmqqbndjjpk5.fsf@gitster.mtv.corp.google.com","threadId":"40254","inReplyTo":"alpine.DEB.1.00.1509030038460.16897@s15462909.onlinehome-server.info","subject":"Re: Do you plan to release 2.5.2 any time soon?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2015-09-03T19:00:42Z","receivedAt":"2015-09-03T19:00:42Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n\n> I have a couple of fixes lined up for bugs in Git for Windows 2.5.1. Do\n> you plan to release 2.5.2 any time soon? If yes, I would hold off,\n> otherwise I will just do a Git for Windows 2.5.1 (Rel 2).\n\nAmong the topics marked for possible later merging to 'maint' in the\ndraft release notes to 2.6, candidates for future maintenance\nsnapshots are:\n\n* mh/get-remote-group-fix # 4 (2 weeks ago) \n* cb/open-noatime-clear-errno # 1 (9 days ago) \n* jk/long-error-messages # 2 (9 days ago) \n* jh/strbuf-read-use-read-in-full # 1 (9 days ago) \n* ps/t1509-chroot-test-fixup # 2 (2 weeks ago) \n* sg/help-group # 1 (8 days ago) \n* nd/dwim-wildcards-as-pathspecs # 1 (9 days ago) \n* jk/fix-alias-pager-config-key-warnings # 1 (3 days ago) \n* jk/rev-list-has-no-notes # 1 (3 days ago) \n* nd/fixup-linked-gitdir # 1 (2 days ago) \n* as/docfix-reflog-expire-unreachable # 1 (8 days ago) \n* sg/t3020-typofix # 1 (8 days ago) \n* po/po-readme # 1 (8 days ago) \n* sg/wt-status-header-inclusion # 1 (8 days ago) \n* ss/fix-config-fd-leak # 1 (8 days ago) \n* jc/calloc-pathspec # 1 (8 days ago) \n* rs/archive-zip-many # 3 (2 days ago) \n* dt/commit-preserve-base-index-upon-opportunistic-cache-tree-update # 1 (2 days ago) \n* cc/trailers-corner-case-fix # 3 (22 hours ago) \n* jk/log-missing-default-HEAD # 1 (22 hours ago) \n* ee/clean-test-fixes # 1 (22 hours ago) \n\nThese I deem are safe (not just the changes themselves are trivially\ncorrect but it is unlikely to make things gravely worse if it turns\nout there were ramifications no reviewers thought about with them)\nand can go in 2.5.2.\n\nAs to other topics that are in 'master' but not in the above list, I\ndo not have doubt about their value (otherwise they would not be in\n'master' in the first place), but either they are still too young in\n'master' or are with sufficiently big impact on the callchain that\nit is not entirely implausible that they have risks of unforeseen\nramifications and fallouts.\n\nLet's aim to tag 2.5.2 soonish, before mid next-week at the latest.\n"},{"id":"269401","messageId":"4fe75c9abad6fea816812beba72988fc@dscho.org","threadId":"40254","inReplyTo":"xmqqbndjjpk5.fsf@gitster.mtv.corp.google.com","subject":"Re: Do you plan to release 2.5.2 any time soon?","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2015-09-04T07:08:13Z","receivedAt":"2015-09-04T07:08:13Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Junio,\n\nOn 2015-09-03 21:00, Junio C Hamano wrote:\n> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n> \n>> I have a couple of fixes lined up for bugs in Git for Windows 2.5.1. Do\n>> you plan to release 2.5.2 any time soon? If yes, I would hold off,\n>> otherwise I will just do a Git for Windows 2.5.1 (Rel 2).\n> \n> Among the topics marked for possible later merging to 'maint' in the\n> draft release notes to 2.6, candidates for future maintenance\n> snapshots are:\n> \n> * mh/get-remote-group-fix # 4 (2 weeks ago) \n> * cb/open-noatime-clear-errno # 1 (9 days ago) \n> * jk/long-error-messages # 2 (9 days ago) \n> * jh/strbuf-read-use-read-in-full # 1 (9 days ago) \n> * ps/t1509-chroot-test-fixup # 2 (2 weeks ago) \n> * sg/help-group # 1 (8 days ago) \n> * nd/dwim-wildcards-as-pathspecs # 1 (9 days ago) \n> * jk/fix-alias-pager-config-key-warnings # 1 (3 days ago) \n> * jk/rev-list-has-no-notes # 1 (3 days ago) \n> * nd/fixup-linked-gitdir # 1 (2 days ago) \n> * as/docfix-reflog-expire-unreachable # 1 (8 days ago) \n> * sg/t3020-typofix # 1 (8 days ago) \n> * po/po-readme # 1 (8 days ago) \n> * sg/wt-status-header-inclusion # 1 (8 days ago) \n> * ss/fix-config-fd-leak # 1 (8 days ago) \n> * jc/calloc-pathspec # 1 (8 days ago) \n> * rs/archive-zip-many # 3 (2 days ago) \n> * dt/commit-preserve-base-index-upon-opportunistic-cache-tree-update #\n> 1 (2 days ago)\n> * cc/trailers-corner-case-fix # 3 (22 hours ago) \n> * jk/log-missing-default-HEAD # 1 (22 hours ago) \n> * ee/clean-test-fixes # 1 (22 hours ago) \n> \n> These I deem are safe (not just the changes themselves are trivially\n> correct but it is unlikely to make things gravely worse if it turns\n> out there were ramifications no reviewers thought about with them)\n> and can go in 2.5.2.\n> \n> As to other topics that are in 'master' but not in the above list, I\n> do not have doubt about their value (otherwise they would not be in\n> 'master' in the first place), but either they are still too young in\n> 'master' or are with sufficiently big impact on the callchain that\n> it is not entirely implausible that they have risks of unforeseen\n> ramifications and fallouts.\n> \n> Let's aim to tag 2.5.2 soonish, before mid next-week at the latest.\n\nOkay!\n\nThank you,\nDscho\n"}]}