chamons / clio Goto Github PK

View Code? Open in Web Editor NEW

4.0 4.0 5.0 181 KB

Generate bug listings for release notes from git history

License: Other

C# 98.75% Makefile 1.00% Shell 0.25%

clio's People

Contributors

Stargazers

Forkers

sgmunn akoeplinger whitneyschmidt prmallic mandel-macaque

clio's Issues

PR Workflow

As all commits these days come in via PRs, we should create a mode (the default one?) that just dumps all PRs between the hashes.

We may need some filters, and to figure out how PRs from PRs (mono bump) are handled.

clio should scan existing release notes and ignore already posted items.

Same issue # on GH and BZ can result in false positives.

The issue is that we have a likely hood of matching a BZ bug and a GH issue depending on how the user formats the commit.

I think, fixes https://github.com/mono/monodevelop/issues/3649 matches GH and BZ (one with a high confidence and one with a likely confidence).

Can we use those confidences to heuristically defer to the one with a higher confidence (before validation)?

Handle branches better

clio gets easily confused with xcode support branche on release.

Main/title links are to PR# not issues

* [6368](https://github.com/xamarin/xamarin-macios/issues/6368) - [d16-2] [CoreGraphics] Fix lifetime of delegates passed to CGPatternCreate.
	 * [CoreGraphics] Fix lifetime of delegates passed to CGPatternCreate. (#6368)
	 * 06/20/2019
	 * [https://github.com/xamarin/xamarin-macios/commit/97c552e56974ac26235d5f2d4954e3f40b12abdf](https://github.com/xamarin/xamarin-macios/commit/97c552e56974ac26235d5f2d4954e3f40b12abdf)
	 * [https://github.com/xamarin/xamarin-macios/issues/6356](https://github.com/xamarin/xamarin-macios/issues/6356)

Remove bugzilla and VSTS support

We're not fixing \ running into bugzilla bugs anymore, and no one is using the VSTS support.

It would simplify the code, and bugzilla takes a lot of the runtime to query.

Clio no longer accepts relative paths for git dirs


Unhandled Exception: LibGit2Sharp.RepositoryNotFoundException: Path '.' doesn't point at a valid Git repository or workdir.
   at LibGit2Sharp.Core.Proxy.git_repository_open(String path)
   at LibGit2Sharp.Repository..ctor(String path, RepositoryOptions options, RepositoryRequiredParameter requiredParameter)
   at Clio.Ranges.RepositoryValidator.HandleBranchRange(String path, String baseBranch, String branch) in /Users/donblas/Programming/clio/src/Clio.Ranges/RepositoryValidator.cs:line 29
   at Clio.Ranges.RepositoryValidator.ValidateGitHashes(String path, ISearchRange range) in /Users/donblas/Programming/clio/src/Clio.Ranges/RepositoryValidator.cs:line 14
   at Clio.Program.Main(String[] args) in /Users/donblas/Programming/clio/src/Clio/EntryPoint.cs:line 96
   at Clio.Program.<Main>(String[] args)

Workaround: realpath .

clio should better handle merge heads

This does not do the "right thing" (15.7 -> 15.8 from master)

~/bin/clio/clio --oldest:273824b3d7ecf41c2f98fd399d632e84dc404c6e --newest:e85a7be881e42f7346827750f72b2d8c3fcafb77 .

but it matches what git log gives us. We get a ton of merge commits and stuff we don't care about.

Warn if branches don't exist locally

Issue title is missing (PR title showed twice)

That might be related to the wrong number (PR instead of issue) being shown

E.g.

* [6188](https://github.com/xamarin/xamarin-macios/issues/6188) - [d16-2] [msbuild] Lock variables accessed in a Parallel.ForEach callback. Fixes #6008.
	 * [msbuild] Lock variables accessed in a Parallel.ForEach callback. (#6188)
	 * 06/03/2019
	 * [https://github.com/xamarin/xamarin-macios/commit/82d0a654009ed600fd2a7c15af3a8937e961d50c](https://github.com/xamarin/xamarin-macios/commit/82d0a654009ed600fd2a7c15af3a8937e961d50c)
	 * [https://github.com/xamarin/xamarin-macios/issues/6008](https://github.com/xamarin/xamarin-macios/issues/6008)
	 * [https://github.com/xamarin/xamarin-macios/issues/6173](https://github.com/xamarin/xamarin-macios/issues/6173)

never shows random "The "Codesign" task failed unexpectedly." which is the issue's description

Clio does not provide any indication that it is running

Clio looks like it is hanging, it would be great if there was a simple cmd line printout like "recounting history..." so that users can know that they correctly wrote the command (and the app is not simply hanging).

Validate Target Milestone on bugs for a given release

Should look for backports and note differences?

Actively not sure on how to do this.

Feedback from #50

Test Bug

Used by clio tests to test itself

Add tag filtering and output

We should generate a set of tags we sort by / output in printing.

Yell if not closed

Text output not optimal

If a gist looks like https://gist.github.com/chamons/26ff1d1d682c8bb6141496a90338762e

then it's impossible to click on the links (so a bunch of copy/paste must be done)

If the same text is turned into a mark-down file like https://gist.github.com/spouliot/7d054de198e9cdc4ec3bdee2cdc81574

the you can click but you can't copy/paste the description into the release notes

Ideally we need the later and a textual (copy/paste-able) version of the description

Clio UX for editing large lists needs work (False positives and bad guesses)

not for this release but we need to think about what clio produce - it does a lot but when it’s wrong there’s no easy way to go back and figure out what the output should have been 😐
E.g.
* GitHub [1](https://github.com/xamarin/xamarin-macios/issues/1) - `make install` does not work unless `make all` is already complete / Add a UserType flag for registered types, and use it to improve the performance for is_user_type. (#5017)
it’s not issue #1 - it’s PR 5017
but to find what issue that PR fixed I need to open a web browser & type the URL

Remove sorting

https://github.com/chamons/clio/blob/master/src/BugCollector.cs#L31

The sorting is only needed due to bugzilla, which is mostly dead, so let's stop.

Should list cross repro as lower priority and not ignore

clio not accepting github over bugzilla

This bug should parse as github not bugzilla

ae5b6631a90cf5dee5a22c11dc8474b36d577634

* Bugzilla [3513](https://bugzilla.xamarin.com/show_bug.cgi?id=3513) - Deploy to device should clear status bar message on start / [linker] Find linked away interfaces when resolving removed interfaces. Fixes #3513. (#3515) (#3524)

Option to split enhans vs bugs

Remove VSTS?

No one is actively using it, and we could simplify a bunch of code.

clio bugzilla not handling context correctly

The relevant test:

CommitWithMultipleBugs_ShowsAllBugs

appears broken w\ async changes.

add an option to gather all contributors in a release

clio should detect and note "foreign" PR notes and stop guessing

Items like Fixes https://github.com/xamarin/maccore/issues/762 this

when parsing with --github=xamarin/xamarin-macios shouldn't resolve to

GitHub 762

We should note they don't match and make it either potential or better yet make a new area for it.

Links to (mono/other) issues are generated as inside xamarin-macios

E.g.

* [6309](https://github.com/xamarin/xamarin-macios/issues/6309) - Bump mono to the latests head and sync with android on 52f6ea14
	 * Bump mono to the latests head and sync with android on 52f6ea14 (#6309)
	 * 06/20/2019
	 * [https://github.com/xamarin/xamarin-macios/commit/3ea877bd915a664dd763a1d0ce9b56701fbfd37a](https://github.com/xamarin/xamarin-macios/commit/3ea877bd915a664dd763a1d0ce9b56701fbfd37a)
	 * [https://github.com/xamarin/xamarin-macios/issues/14836](https://github.com/xamarin/xamarin-macios/issues/14836)
	 * [https://github.com/xamarin/xamarin-macios/issues/13873](https://github.com/xamarin/xamarin-macios/issues/13873)

There is no such https://github.com/xamarin/xamarin-macios/issues/13873 issue or PR inside xamarin-macios (yet!)

Some comments from 15.8 preview 1

Based on the list of xamarin-macios issues I added some comments on how clio could have produced a more accurate list
https://gist.github.com/chamons/4965fbcbf3df2ad0a074ebbf59b2f367

Output for mono bumps is not very useful

There might be interesting/applicable things inn the bumps but the tool output is not helpful to identify them quickly.

* [6309](https://github.com/xamarin/xamarin-macios/issues/6309) - Bump mono to the latests head and sync with android on 52f6ea14
	 * Bump mono to the latests head and sync with android on 52f6ea14 (#6309)
	 * 06/20/2019
	 * [https://github.com/xamarin/xamarin-macios/commit/3ea877bd915a664dd763a1d0ce9b56701fbfd37a](https://github.com/xamarin/xamarin-macios/commit/3ea877bd915a664dd763a1d0ce9b56701fbfd37a)
	 * [https://github.com/xamarin/xamarin-macios/issues/14836](https://github.com/xamarin/xamarin-macios/issues/14836)
	 * [https://github.com/xamarin/xamarin-macios/issues/13873](https://github.com/xamarin/xamarin-macios/issues/13873)

* [6215](https://github.com/xamarin/xamarin-macios/issues/6215) - [d16-2] Bump mono to 2019-02 latest head.
	 * Bump mono to 2019-02 latests head. (#6215)
	 * 06/07/2019
	 * [https://github.com/xamarin/xamarin-macios/commit/2f1cc7bb8060e33a45f5973bc581bfafeccfb3c6](https://github.com/xamarin/xamarin-macios/commit/2f1cc7bb8060e33a45f5973bc581bfafeccfb3c6)
	 * [https://github.com/xamarin/xamarin-macios/issues/14214](https://github.com/xamarin/xamarin-macios/issues/14214)


* [6192](https://github.com/xamarin/xamarin-macios/issues/6192) - [d16-2] Bump mono.
	 * Bump mono. (#6192)
	 * 06/03/2019
	 * [https://github.com/xamarin/xamarin-macios/commit/f7d7c7668a25873aeee5d6f930d0f26c3d354246](https://github.com/xamarin/xamarin-macios/commit/f7d7c7668a25873aeee5d6f930d0f26c3d354246)

* [6134](https://github.com/xamarin/xamarin-macios/issues/6134) - [d16-2] Bump mono.
	 * Bump mono. (#6134)
	 * 05/28/2019
	 * [https://github.com/xamarin/xamarin-macios/commit/4400ca4ac076e57d919274c508f78d334e144524](https://github.com/xamarin/xamarin-macios/commit/4400ca4ac076e57d919274c508f78d334e144524)
	 * [https://github.com/xamarin/xamarin-macios/issues/14637](https://github.com/xamarin/xamarin-macios/issues/14637)
	 * [https://github.com/xamarin/xamarin-macios/issues/14632](https://github.com/xamarin/xamarin-macios/issues/14632)
	 * [https://github.com/xamarin/xamarin-macios/issues/13600](https://github.com/xamarin/xamarin-macios/issues/13600)
	 * [https://github.com/xamarin/xamarin-macios/issues/14627](https://github.com/xamarin/xamarin-macios/issues/14627)
	 * [https://github.com/xamarin/xamarin-macios/issues/14616](https://github.com/xamarin/xamarin-macios/issues/14616)
	 * [https://github.com/xamarin/xamarin-macios/issues/14069](https://github.com/xamarin/xamarin-macios/issues/14069)

* [6053](https://github.com/xamarin/xamarin-macios/issues/6053) - [d16-2] Bump mono to head of 2019-02
	 * [d16-2] Bump mono to head of 2019-02 (#6053)
	 * 05/16/2019
	 * [https://github.com/xamarin/xamarin-macios/commit/b34393e6801d61850bcc31b9dbb3b2c1ca0c1756](https://github.com/xamarin/xamarin-macios/commit/b34393e6801d61850bcc31b9dbb3b2c1ca0c1756)
	 * [https://github.com/xamarin/xamarin-macios/issues/13717](https://github.com/xamarin/xamarin-macios/issues/13717)
	 * [https://github.com/xamarin/xamarin-macios/issues/14437](https://github.com/xamarin/xamarin-macios/issues/14437)
	 * [https://github.com/xamarin/xamarin-macios/issues/14438](https://github.com/xamarin/xamarin-macios/issues/14438)
	 * [https://github.com/xamarin/xamarin-macios/issues/14448](https://github.com/xamarin/xamarin-macios/issues/14448)
	 * [https://github.com/xamarin/xamarin-macios/issues/14445](https://github.com/xamarin/xamarin-macios/issues/14445)
	 * [https://github.com/xamarin/xamarin-macios/issues/14452](https://github.com/xamarin/xamarin-macios/issues/14452)
	 * [https://github.com/xamarin/xamarin-macios/issues/14428](https://github.com/xamarin/xamarin-macios/issues/14428)
	 * [https://github.com/xamarin/xamarin-macios/issues/14423](https://github.com/xamarin/xamarin-macios/issues/14423)
	 * [https://github.com/xamarin/xamarin-macios/issues/14409](https://github.com/xamarin/xamarin-macios/issues/14409)
	 * [https://github.com/xamarin/xamarin-macios/issues/14413](https://github.com/xamarin/xamarin-macios/issues/14413)
	 * [https://github.com/xamarin/xamarin-macios/issues/14387](https://github.com/xamarin/xamarin-macios/issues/14387)

Maybe we should re-spawn Clio to process the mono hash (from the original hash to the latest hash) ?

chamons / clio Goto Github PK

clio's People

Contributors

Stargazers

Forkers

clio's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs