Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

2018-02-20 Thread Gabe Harbs
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. >

Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

2018-02-20 Thread Alex Harui
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

Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

2018-02-20 Thread Gabe Harbs
+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

Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

2018-02-20 Thread Alex Harui
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

Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

2018-02-20 Thread Piotr Zarzycki
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

Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

2018-02-14 Thread Carlos Rovira
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

Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

2018-02-14 Thread 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 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

Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

2018-02-14 Thread Olaf Krueger
>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/

Re: Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

2018-02-14 Thread Olaf Krueger
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]

Maintain Release Notes List of changes(was: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released)

2018-02-14 Thread Carlos Rovira
Hi, in order to move this, I think this is important, and we should have as a team some way to make this possible. We should make this happen for the next release. Suggestions are welcome. Thanks! Carlos 2018-02-14 13:56 GMT+01:00 Carlos Rovira : > That's right, we

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

2018-02-14 Thread Carlos Rovira
That's right, we should do something in that way. Maybe better create a new thread about this 2018-02-14 13:45 GMT+01:00 Piotr Zarzycki : > In Moonshine we are following this -> http://keepachangelog.com/en/1.0.0/ > > 2018-02-14 13:44 GMT+01:00 Gabe Harbs

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

2018-02-14 Thread Piotr Zarzycki
In Moonshine we are following this -> http://keepachangelog.com/en/1.0.0/ 2018-02-14 13:44 GMT+01:00 Gabe Harbs : > We probably should maintain a changelog which gets modified as things are > developed. > > > On Feb 14, 2018, at 2:39 PM, Carlos Rovira

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

2018-02-14 Thread Gabe Harbs
We probably should maintain a changelog which gets modified as things are developed. > On Feb 14, 2018, at 2:39 PM, Carlos Rovira wrote: > > Hi just one more thing, for next release, since this is already done and > announced. > > People in twitter and facebook asked

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

2018-02-14 Thread Carlos Rovira
Hi just one more thing, for next release, since this is already done and announced. People in twitter and facebook asked about "what's changed" when released 0.9.0 (in comparison with FlexJS latest release) My response was that 0.9.0 was a first release here and there was no "list of changes".

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

2018-02-13 Thread Jason Guild
Please pull the first sentence from the 0.9.0 blog announcement that Carlos recently worked on. It reads better and is grammatically correct. On 2/13/2018 12:15 PM, Alex Harui wrote: We will wait a bit for other feedback and let the mirrors finish propagating. I'll post it in about 8 hours if

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

2018-02-13 Thread Alex Harui
We will wait a bit for other feedback and let the mirrors finish propagating. I'll post it in about 8 hours if no other feedback. -Alex On 2/13/18, 1:00 PM, "Piotr Zarzycki" wrote: >Go on and announce. I will fill GitHub release once it will be done! :) > >Thanks,

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

2018-02-13 Thread Piotr Zarzycki
Go on and announce. I will fill GitHub release once it will be done! :) Thanks, Piotr 2018-02-13 21:57 GMT+01:00 Andrew Wetmore : > This announcement seems clear and inviting. > > On Tue, Feb 13, 2018 at 3:06 PM, Alex Harui > wrote: > > > Please

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

2018-02-13 Thread Andrew Wetmore
This announcement seems clear and inviting. On Tue, Feb 13, 2018 at 3:06 PM, Alex Harui wrote: > Please comment on the draft below. > > Thoughts? > -Alex > > -- Andrew Wetmore http://cottage14.blogspot.com/

Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.1 Released

2018-02-13 Thread Alex Harui
FYI, I just noticed that the "Get Started" section in the docs needs filling out so I'm working on that now. -Alex On 2/13/18, 11:06 AM, "Alex Harui" wrote: >Please comment on the draft below. > >Thoughts? >-Alex > >--- > >The Apache Royale community is