I think we shouldn't base anything on _now_ so we don't have a moving target. In any case, we just have to choose one method, and what we choose we can just cache a snapshot of it, consistently, to mark possible trends. I used to compile stats manually but abandoned it: https://github.com/apache/cordova-apache-board-reports/blob/master/2014/stats.json On Thu, Sep 20, 2018 at 6:19 PM Jan Piotrowski <[email protected]> wrote: > > Yes, "reading" those numbers is unfortunately not trivial - I had to > rewrite those queries _a lot_ until they made some sense without knots > in my brain. > > Here is the explanation for what you see: > > > Referring to Sept Q3. > > > > Issues created - 103 open, 62 closed --> 165 total issues created > > Issues closed - 53 closed --> 9 issues less from 62 above > > Issues created: In Q3 a total of 165 issues were created. Of those > 165, _right now_ 103 are open and 62 are closed. > Issues closed: In Q3 a total of 53 issues were closed (although those > could have been created in Q3, Q2, Q1...) > > > PRs created - 51 open, 257 closed/merged --> 308 total PRs created > > PRs closed/merged - 299 closed/merged --> 9 issues less from 308 above > > Same for PRs: > PRs created: In Q3 a total of 308 PRs were created. Of those 308, > _right now_ 51 are still open and 257 are closed/merged. > PRs closed/merged: In Q3 a total of 299 PRs were closed/merged > (although those could have been created any time in the past) > > The "created" query chooses items based on their `created` date, the > "closed" query based on `closed` date. > > Maybe the open/closed for the "created" queries should not be > considered, as it is based on _now_ and can change over time (when > more of those items are closed as time progresses). > (On the other hand: It can be useful to know how many of the new items > are already taken care of already.) > > Does that make sense? > Or should we have different queries? > Any idea how to better represent and document the current situation? > > J > > 2018-09-17 3:36 GMT+02:00 Shazron <[email protected]>: > > Copy pasta mistake. Should be: > > PRs closed/merged - 299 closed/merged --> 9 issues less from 308 above > > On Mon, Sep 17, 2018 at 9:36 AM Shazron <[email protected]> wrote: > >> > >> Thanks Jan! > >> Some issues with the queries, the math doesn't add up. > >> > >> Referring to Sept Q3. > >> > >> Issues created - 103 open, 62 closed --> 165 total issues created > >> Issues closed - 53 closed --> 9 issues less from 62 above > >> > >> PRs created - 51 open, 257 closed/merged --> 308 total PRs created > >> PRs closed/merged - 299 closed/merged --> 9 issues less from 62 above > >> > >> The small discrepancy is no big deal for now -- I'll take the stats from > >> the 'Created' query for the board report. > >> On Sat, Sep 15, 2018 at 2:32 AM Jan Piotrowski <[email protected]> > >> wrote: > >> > > >> > http://cordova.betamo.de/cordova-board-reports-issue-and-pr-searches.php > >> > now exists and displays for multiple quarters (past and present) links > >> > to GitHub searches that show: > >> > > >> > - Issues created in quarter (displays individually how many of those > >> > still open and how many closed) > >> > - Issues closed in quarter > >> > - PRs created in quarter (displays individually how many of those > >> > still open and how many closed/merged) > >> > - PRs merged in quarter > >> > - PRs closed in quarter > >> > - PRs closed or merged in quarter > >> > > >> > Anything missing? > >> > Please check my queries an logic - I might have a knot in my brain now > >> > from the unmerged/closed/merged stuff now. > >> > > >> > It might be worth reporting "open issues and open PRs right now", but > >> > I was not able to think how to build this in a search query for any > >> > point of time. Anyone an idea? > >> > > >> > -J > >> > > >> > 2018-09-14 18:56 GMT+02:00 Shazron <[email protected]>: > >> > > Let's get this process down right for next quarter, if we don't get it > >> > > in time for this one. > >> > > Yes, the reporting dates are in the README for tge repo for the draft > >> > > report. > >> > > On Fri, Sep 14, 2018 at 7:32 PM Jan Piotrowski <[email protected]> > >> > > wrote: > >> > >> > >> > >> Thanks for pulling me in here julio. > >> > >> > >> > >> http://cordova.betamo.de/cordova-github-issues-search-strings.php > >> > >> creates the search strings for all issues on all repositories (bottom > >> > >> left). > >> > >> > >> > >> Just adding the time frame doesn't work, with `created:>2018-06-01 > >> > >> created:<2018-09-01` added at the end, it seems the second `created` > >> > >> is overwriting the first one and returns all issues until 09-01. > >> > >> > >> > >> But you can exclude all before and after the relevant dates with > >> > >> `-created:<2018-06-01 -created:>2018-09-01`: > >> > >> https://github.com/issues?utf8=%E2%9C%93&q=is%3Aissue+repo%3Aapache%2Fcordova-android+repo%3Aapache%2Fcordova-ios+repo%3Aapache%2Fcordova-windows+repo%3Aapache%2Fcordova-browser+repo%3Aapache%2Fcordova-osx+repo%3Aapache%2Fcordova-test-platform+repo%3Aapache%2Fcordova-electron+repo%3Aapache%2Fcordova-blackberry+repo%3Aapache%2Fcordova-firefoxos+repo%3Aapache%2Fcordova-ubuntu+repo%3Aapache%2Fcordova-wp8+repo%3Aapache%2Fcordova-tizen+repo%3Aapache%2Fcordova-qt+repo%3Aapache%2Fcordova-webos+repo%3Aapache%2Fcordova-amazon-fireos+repo%3Aapache%2Fcordova-wp7+repo%3Aapache%2Fcordova-bada+repo%3Aapache%2Fcordova-bada-wac+repo%3Aapache%2Fcordova-plugin-battery-status+repo%3Aapache%2Fcordova-plugin-camera+repo%3Aapache%2Fcordova-plugin-device+repo%3Aapache%2Fcordova-plugin-dialogs+repo%3Aapache%2Fcordova-plugin-file+repo%3Aapache%2Fcordova-plugin-geolocation+repo%3Aapache%2Fcordova-plugin-inappbrowser+repo%3Aapache%2Fcordova-plugin-media+repo%3Aapache%2Fcordova-plugin-media-capture+repo%3Aapache%2Fcordova-plugin-network-information+repo%3Aapache%2Fcordova-plugin-screen-orientation+repo%3Aapache%2Fcordova-plugin-splashscreen+repo%3Aapache%2Fcordova-plugin-statusbar+repo%3Aapache%2Fcordova-plugin-vibration+repo%3Aapache%2Fcordova-plugin-whitelist+repo%3Aapache%2Fcordova-plugin-wkwebview-engine+repo%3Aapache%2Fcordova-plugins+repo%3Aapache%2Fcordova-plugin-console+repo%3Aapache%2Fcordova-plugin-contacts+repo%3Aapache%2Fcordova-plugin-device-motion+repo%3Aapache%2Fcordova-plugin-device-orientation+repo%3Aapache%2Fcordova-plugin-file-transfer+repo%3Aapache%2Fcordova-plugin-globalization+repo%3Aapache%2Fcordova-plugin-legacy-whitelist+repo%3Aapache%2Fcordova-cli+repo%3Aapache%2Fcordova-plugman+repo%3Aapache%2Fcordova-coho+repo%3Aapache%2Fcordova-js+repo%3Aapache%2Fcordova-lib+repo%3Aapache%2Fcordova-common+repo%3Aapache%2Fcordova-create+repo%3Aapache%2Fcordova-fetch+repo%3Aapache%2Fcordova-serve+repo%3Aapache%2Fcordova-plugin-test-framework+repo%3Aapache%2Fcordova-paramedic+repo%3Aapache%2Fcordova-mobile-spec+repo%3Aapache%2Fcordova-app-hello-world+repo%3Aapache%2Fcordova-template-reference+repo%3Aapache%2Fcordova-docs+repo%3Aapache%2Fcordova-status+repo%3Aapache%2Fcordova-contribute+repo%3Aapache%2Fcordova-discuss+repo%3Aapache%2Fcordova-apache-board-reports+repo%3Aapache%2Fcordova-new-committer-and-pmc+repo%3Aapache%2Fcordova-node-xcode+repo%3Aapache%2Fcordova-medic+repo%3Aapache%2Fcordova-labs+repo%3Aapache%2Fcordova-weinre+repo%3Aapache%2Fcordova-app-harness+repo%3Aapache%2Fcordova-plugin-compat+repo%3Aapache%2Fcordova-registry-web+repo%3Aapache%2Fcordova-registry+repo%3Aapache%2Fcordova-fauxton-server+-created%3A%3C2018-06-01+-created%3A%3E2018-09-01+ > >> > >> (via https://stackoverflow.com/a/50183610/252627) > >> > >> > >> > >> Is that what we are looking for? > >> > >> > >> > >> We can probably also search for "PRs closed in quarter" using > >> > >> https://help.github.com/articles/searching-issues-and-pull-requests/#search-by-when-an-issue-or-pull-request-was-closed > >> > >> > >> > >> > >> > >> If so, I can quickly add the generation of these search links to > >> > >> cordova.betamo.de as well. Our quarter starts in June, correct? > >> > >> > >> > >> J > >> > >> > >> > >> 2018-09-14 13:17 GMT+02:00 julio cesar sanchez > >> > >> <[email protected]>: > >> > >> > Jan had some filters to easily see/list bugs, but not sure if it's > >> > >> > possible > >> > >> > to know the number of created/closes issues by quarter. > >> > >> > Will put him in copy just in case he missed the draft and can chime > >> > >> > in to > >> > >> > provide more information. > >> > >> > > >> > >> > El vie., 14 sept. 2018 a las 2:34, Shazron (<[email protected]>) > >> > >> > escribió: > >> > >> >> > >> > >> >> What Julio said -- broad strokes only. > >> > >> >> Julio -- if we have those numbers, we could add them. Unless it's > >> > >> >> an > >> > >> >> automatic process, it won't be reliable. > >> > >> >> On Thu, Sep 13, 2018 at 7:35 PM julio cesar sanchez > >> > >> >> <[email protected]> wrote: > >> > >> >> > > >> > >> >> > I don't think that information is relevant for the report, as > >> > >> >> > what we > >> > >> >> > usually include are releases and information about them, so it's > >> > >> >> > something > >> > >> >> > we should mention when we release the master changes, not before. > >> > >> >> > > >> > >> >> > As the report talks about JIRA issues and we moved to github > >> > >> >> > issues, > >> > >> >> > should > >> > >> >> > we add the number of github issues created/closed? > >> > >> >> > > >> > >> >> > > >> > >> >> > > >> > >> >> > El jue., 13 sept. 2018 a las 13:11, Chris Brody > >> > >> >> > (<[email protected]>) > >> > >> >> > escribió: > >> > >> >> > > >> > >> >> > > There was a lot of work done on master branch for next major > >> > >> >> > > release > >> > >> >> > > in > >> > >> >> > > areas such as performance improvements, internal API cleanup, > >> > >> >> > > migtation > >> > >> >> > > away from shelljs, major test improvements that seem to be > >> > >> >> > > missing. > >> > >> >> > > > >> > >> >> > > On Thu, Sep 13, 2018, 12:14 AM Shazron <[email protected]> > >> > >> >> > > wrote: > >> > >> >> > > > >> > >> >> > > > Please review and comment > >> > >> >> > > > > >> > >> >> > > > > >> > >> >> > > > >> > >> >> > > https://github.com/apache/cordova-apache-board-reports/blob/master/2018/2018-09.md > >> > >> >> > > > > >> > >> >> > > > I want to get this out before the end of this week. Thanks! > >> > >> >> > > > > >> > >> >> > > > > >> > >> >> > > > --------------------------------------------------------------------- > >> > >> >> > > > To unsubscribe, e-mail: [email protected] > >> > >> >> > > > For additional commands, e-mail: [email protected] > >> > >> >> > > > > >> > >> >> > > > > >> > >> >> > > > >> > >> >> > >> > >> >> --------------------------------------------------------------------- > >> > >> >> To unsubscribe, e-mail: [email protected] > >> > >> >> For additional commands, e-mail: [email protected] > >> > >> >> > >> > >> > > >> > >> > >> > >> --------------------------------------------------------------------- > >> > >> To unsubscribe, e-mail: [email protected] > >> > >> For additional commands, e-mail: [email protected] > >> > >> > >> > > > >> > > --------------------------------------------------------------------- > >> > > To unsubscribe, e-mail: [email protected] > >> > > For additional commands, e-mail: [email protected] > >> > > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: [email protected] > >> > For additional commands, e-mail: [email protected] > >> > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
