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/co
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
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 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 t
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/me
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 quar
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 wrote:
>
> Thanks for pulling me in here julio.
>
> http://cordova.betamo.de/cor
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 th
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 () escribió:
> What Ju
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
wrote:
>
> I don't think that information is relevant for the report, as what we
> usually includ
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
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 wrote:
> Please review and comment
>
> https:
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: dev-unsubscr...@cordova.apache.org
12 matches
Mail list logo
