No I missed it. Pneumonia and all…
FWIW, it’s possible to add commit references to issues after a commit is made.
You just include a hash in an issue comment.
> On Feb 20, 2018, at 7:13 PM, Alex Harui wrote:
>
> I don't know if you saw my commit wizard idea.
> https://lists.apache.org/thread.h
I don't know if you saw my commit wizard idea.
https://lists.apache.org/thread.html/5d94976d277729a8f34b77a0ec09e45678bbf5
d2d7111e411fb5fb14@%3Cdev.royale.apache.org%3E
I guess it won't help if you don't use command line for commits. It
should be possible to do any of the 3 you suggested. The G
+1
Some thoughts:
1. We can have a utility which rewrites entries to a standard format before
release.
2. We can have a form which takes the info and adds it to the release notes.
3. It might be interesting to have a Github integration which watches Issues
and when a commit closes a ticket, it c
If you want a particular format, help me write a wizard that will manage
that. I will not remember to get it right every time I commit. I will
not know what to use for a description unless we take the bug topic
verbatim with any misspellings and other cruft.
My 2 cents,
-Alex
On 2/20/18, 5:37 A
I see in release notes links to issues. I'm in favor of having description
+ eventually links.
- my description for a bug [Bug Number](link) - it will display nicely on
GitHub.
I'm talking about this commit.
What do other thinks ?
Thanks, Piotr
2018-02-14 23:13 GMT+01:00 Carlos Rovira :
> Ok
Ok Alex, that's great, so we'll be doing the work on RELEASE_NOTES file
thanks!
2018-02-14 17:31 GMT+01:00 Alex Harui :
> We already have this. It is the RELEASE_NOTES file. All ASF releases are
> supposed to have one so we should use it. And as keepachangelog.com says,
> it is not the GitHub
We already have this. It is the RELEASE_NOTES file. All ASF releases are
supposed to have one so we should use it. And as keepachangelog.com says,
it is not the GitHub commit log.
IMO, it is not the Release Manager's job to fill this out. It needs to be
maintained by every committer. I know I
>In Moonshine we are following this -> http://keepachangelog.com/en/1.0.0/
+1, we also start using this format here ;-)
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
We could force ourselves to consequent use GitHub issues and milestones (and
references from commits to issues) and maybe there's a way to generate a
ChangeLog automatically.
I just found e.g. this [1], I guess there exist some more like this out
there...
Just some thoughts,
Olaf
[1] https://gith
