{"thread":{"id":"42611","subject":"[ANNOUNCE] Sharness v1.0.0","startedAt":"2016-06-16T06:55:52Z","lastAt":"2016-06-16T06:55:53Z","messageCount":8,"participants":["Christian Couder","Stefan Beller","Jeff King","Junio C Hamano","Mathias Lafeldt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"289245","messageId":"CAP8UFD0uvaB-2_CrXs2ZvoqLRHfCd8efA-S7-tE2Qa6Pn+rAAg@mail.gmail.com","threadId":"42611","inReplyTo":null,"subject":"[ANNOUNCE] Sharness v1.0.0","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2016-06-14T19:34:17Z","receivedAt":"2016-06-16T06:55:52Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi,\n\nVersion 1.0.0 of Sharness [1] -- the test harness library derived from\nGit's test lib -- is released.\n\nThis release contains many upstream fixes and improvements from Git\nand a lot of specific user contributed features [2].\n\nIt's the first release since v0.3.0 in April 2013 [3].\n\nSharness was first announced on this list in July 2012 [4]. It was\ncreated from Git's test lib in April 2011 by Mathias Lafeldt who\nimproved and maintained it until a few days ago.\n\nThanks a lot Mathias!\n\nThanks also to all the other contributors (by alphabetical order)\nsince the beginning:\n\nAlexander Sulfrian\nDennis Kaarsemaker\nJeff King\nJohn Keeping\nKonstantin Koroviev\nMark A. Grondona\nMatthieu Moy\nMaxim Bublis\nRichard Hansen\nRoman Neuhauser\nSimon Chiang\n\nThanks also to all the Git contributors who improved test-lib.sh as\nmany of the features and fixes come from upstream!\n\nEnjoy,\nChristian.\n\n[1] https://github.com/chriscool/sharness\n[2] https://github.com/chriscool/sharness/blob/master/CHANGELOG.md\n[3] http://thread.gmane.org/gmane.comp.version-control.git/219944/\n[4] http://thread.gmane.org/gmane.comp.version-control.git/201591/\n"},{"id":"289246","messageId":"CAGZ79kYaQTdVoXOGpKbQmWsdRftY10TBZTTf_Ya-fdegykU-QQ@mail.gmail.com","threadId":"42611","inReplyTo":"CAP8UFD0uvaB-2_CrXs2ZvoqLRHfCd8efA-S7-tE2Qa6Pn+rAAg@mail.gmail.com","subject":"Re: [ANNOUNCE] Sharness v1.0.0","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2016-06-14T19:48:18Z","receivedAt":"2016-06-16T06:55:52Z","isPatch":false,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"On Tue, Jun 14, 2016 at 12:34 PM, Christian Couder\n wrote:\n> Hi,\n>\n> Version 1.0.0 of Sharness [1] -- the test harness library derived from\n> Git's test lib -- is released.\n>\n> This release contains many upstream fixes and improvements from Git\n> and a lot of specific user contributed features [2].\n>\n> It's the first release since v0.3.0 in April 2013 [3].\n>\n> Sharness was first announced on this list in July 2012 [4]. It was\n> created from Git's test lib in April 2011 by Mathias Lafeldt who\n> improved and maintained it until a few days ago.\n>\n> Thanks a lot Mathias!\n\nThanks for picking up the work, Christian!\n\nIs there any word out there from Mathias on making you the designated\nnew maintainer? (I cannot tell if this is a genuine maintainer change, or\na [hostile] fork by reading this email, and I don't know much of the context,\nas I did not know git Git test suite was a stand alone thing)\n\nThanks,\nStefan\n\n>\n> Thanks also to all the other contributors (by alphabetical order)\n> since the beginning:\n>\n> Alexander Sulfrian\n> Dennis Kaarsemaker\n> Jeff King\n> John Keeping\n> Konstantin Koroviev\n> Mark A. Grondona\n> Matthieu Moy\n> Maxim Bublis\n> Richard Hansen\n> Roman Neuhauser\n> Simon Chiang\n>\n> Thanks also to all the Git contributors who improved test-lib.sh as\n> many of the features and fixes come from upstream!\n>\n> Enjoy,\n> Christian.\n>\n> [1] https://github.com/chriscool/sharness\n> [2] https://github.com/chriscool/sharness/blob/master/CHANGELOG.md\n> [3] http://thread.gmane.org/gmane.comp.version-control.git/219944/\n> [4] http://thread.gmane.org/gmane.comp.version-control.git/201591/\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n"},{"id":"289251","messageId":"CAP8UFD2wT0Qoxksza1uU1GMTWRD4GcfdYzDTrNh+JLtfT9h3rA@mail.gmail.com","threadId":"42611","inReplyTo":"CAGZ79kYaQTdVoXOGpKbQmWsdRftY10TBZTTf_Ya-fdegykU-QQ@mail.gmail.com","subject":"Re: [ANNOUNCE] Sharness v1.0.0","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2016-06-14T21:13:31Z","receivedAt":"2016-06-16T06:55:52Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Tue, Jun 14, 2016 at 9:48 PM, Stefan Beller wrote:\n> On Tue, Jun 14, 2016 at 12:34 PM, Christian Couder\n> wrote:\n>>\n>> Sharness was first announced on this list in July 2012 [4]. It was\n>> created from Git's test lib in April 2011 by Mathias Lafeldt who\n>> improved and maintained it until a few days ago.\n>>\n>> Thanks a lot Mathias!\n>\n> Thanks for picking up the work, Christian!\n>\n> Is there any word out there from Mathias on making you the designated\n> new maintainer? (I cannot tell if this is a genuine maintainer change, or\n> a [hostile] fork by reading this email, and I don't know much of the context,\n\nMathias gave me commiter rights on the repo\n(https://github.com/mlafeldt/sharness at that time) one year ago.\n\nA few days ago, as I wanted since last December to release v1.0.0, but\nwas uneasy to do so without at least a LGTM from him, I contacted him\nby private email and he decided to transfer the repo to\nhttps://github.com/chriscool/sharness, to give me maintainership and\nto step down completely. So yeah this is a genuine maintainer change\nand not an hostile fork at all.\n(I cc'ed Mathias again so he can confirm if he wants.)\n\n> as I did not know git Git test suite was a stand alone thing)\n\nI am not sure it qualifies as a stand alone thing there are some\ndifferences and for now some features are going from Git's test-lib.sh\ninto Sharness but not the other way around.\n"},{"id":"289255","messageId":"20160614213453.GA21560@sigill.intra.peff.net","threadId":"42611","inReplyTo":"CAP8UFD0uvaB-2_CrXs2ZvoqLRHfCd8efA-S7-tE2Qa6Pn+rAAg@mail.gmail.com","subject":"Re: [ANNOUNCE] Sharness v1.0.0","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-06-14T21:34:53Z","receivedAt":"2016-06-16T06:55:52Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Jun 14, 2016 at 09:34:17PM +0200, Christian Couder wrote:\n\n> Version 1.0.0 of Sharness [1] -- the test harness library derived from\n> Git's test lib -- is released.\n\nCool. Git's test harness is something I really miss having in other\nprojects. I'm glad this project exists. :)\n\n> This release contains many upstream fixes and improvements from Git\n> and a lot of specific user contributed features [2].\n\nIt looks like it takes some manual work to massage upstream improvements\ninto Sharness.\n\nI don't think the Git project would ever want to say \"sharness is the\nupstream, and we are now just a user of it\". But I wonder if we could\nbreak down test-lib.sh to keep the Git-specific parts separate, which\nwould make it easier for sharness to pull the other bits as a whole.\n\nI dunno. I guess it would depend on how invasive the patches were, but I\nwould not be opposed to such a thing. I suspect the separation might\nactually make our test setup more clear.\n\n-Peff\n"},{"id":"289257","messageId":"xmqq7fdr8n0o.fsf@gitster.mtv.corp.google.com","threadId":"42611","inReplyTo":"20160614213453.GA21560@sigill.intra.peff.net","subject":"Re: [ANNOUNCE] Sharness v1.0.0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-06-14T21:43:19Z","receivedAt":"2016-06-16T06:55:53Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King writes:\n\n> I don't think the Git project would ever want to say \"sharness is the\n> upstream, and we are now just a user of it\". But I wonder if we could\n> break down test-lib.sh to keep the Git-specific parts separate, which\n> would make it easier for sharness to pull the other bits as a whole.\n\nI took a quick look around, and it seems that this is an outdated\nfork made without getting much of the improvement from its upstream\nsince it forked. It does not seem to have lazy prerequisite, for\nexample.\n"},{"id":"289259","messageId":"20160614214655.GA22334@sigill.intra.peff.net","threadId":"42611","inReplyTo":"xmqq7fdr8n0o.fsf@gitster.mtv.corp.google.com","subject":"Re: [ANNOUNCE] Sharness v1.0.0","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2016-06-14T21:46:55Z","receivedAt":"2016-06-16T06:55:53Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Jun 14, 2016 at 02:43:19PM -0700, Junio C Hamano wrote:\n\n> Jeff King writes:\n> \n> > I don't think the Git project would ever want to say \"sharness is the\n> > upstream, and we are now just a user of it\". But I wonder if we could\n> > break down test-lib.sh to keep the Git-specific parts separate, which\n> > would make it easier for sharness to pull the other bits as a whole.\n> \n> I took a quick look around, and it seems that this is an outdated\n> fork made without getting much of the improvement from its upstream\n> since it forked. It does not seem to have lazy prerequisite, for\n> example.\n\nYeah, I don't think it has kept up with our work. My statement above was\n\"I don't think we'd _ever_ want to consider sharness the upstream, even\nif it were up to date\", but obviously there would be a lot of work to\neven get it there.\n\n-Peff\n"},{"id":"289261","messageId":"xmqqy467784a.fsf@gitster.mtv.corp.google.com","threadId":"42611","inReplyTo":"20160614214655.GA22334@sigill.intra.peff.net","subject":"Re: [ANNOUNCE] Sharness v1.0.0","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-06-14T21:50:29Z","receivedAt":"2016-06-16T06:55:53Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King writes:\n\n> Yeah, I don't think it has kept up with our work. My statement above was\n> \"I don't think we'd _ever_ want to consider sharness the upstream, even\n> if it were up to date\", but obviously there would be a lot of work to\n> even get it there.\n\nI actually was a lot more optimistic when they started, and if it\nwere up to date, I would have at least tried to see what the damage\nto our t/ part will be if we swapped t/test-lib{,-functions}.sh with\nit, which was the original reason why I took a look until I found\nout that it did not have some things.\n"},{"id":"289282","messageId":"CAMFa-2gKpm2jLiYGVrdkrhvo5uzqdq+rNJhuyFrWL+LbnhHSWg@mail.gmail.com","threadId":"42611","inReplyTo":"CAP8UFD2wT0Qoxksza1uU1GMTWRD4GcfdYzDTrNh+JLtfT9h3rA@mail.gmail.com","subject":"Re: [ANNOUNCE] Sharness v1.0.0","fromName":"Mathias Lafeldt","fromEmail":"mathias.lafeldt@gmail.com","sentAt":"2016-06-15T09:03:51Z","receivedAt":"2016-06-16T06:55:53Z","isPatch":false,"sender":{"key":"mathias.lafeldt@gmail.com","avatar":"https://gravatar.com/avatar/8657fba2d2c19d0524e5832717b41b68b54ff6e4a331b745027a135c1dbc61c5?d=mp&s=160"},"body":">> Is there any word out there from Mathias on making you the designated\n>> new maintainer? (I cannot tell if this is a genuine maintainer change, or\n>> a [hostile] fork by reading this email, and I don't know much of the context,\n\nYes, it's 100% genuine. I handed over maintenance to Christian Couder.\n\nHere's a signed commit to prove the transfer:\nhttps://github.com/chriscool/sharness/pull/55\n\n(Sorry for double posting, the mailing list didn't like my first email.)\n\n-- \n-Mathias\nhttps://tinyletter.com/production-ready\n"}]}