Regarding jira

[Zachary Gorden]

Timo originally proposed this but I'd like to actually see the
proposal implemented. When working on ReactOS, I'd like developers to
create tickets in jira that their commits can then reference. For
example, Amine's wine syncs could have a ticket with the title "Wine
sync with version 1.x.y" or Alex's NPFS rewrite could have a ticket
with the title "New NPFS driver" and the relevant commits can have the
ticket number in them. This way when time comes for the changelog, all
that needs to be done is gather a list of all tickets closed before
the branch, no more of the digging through thousands of commit
messages crap.

[Aleksey Bragin]

On 17.09.2013 20:47, Zachary Gorden wrote:
>   Timo originally proposed this but I'd like to
> actually see the
>  proposal implemented. When working on ReactOS, I'd like developers to
>  create tickets in jira that their commits can then reference. For
>  example, Amine's wine syncs could have a ticket with the title "Wine
>  sync with version 1.x.y" or Alex's NPFS rewrite could have a ticket
>  with the title "New NPFS driver" and the relevant commits can have the
>  ticket number in them. This way when time comes for the changelog, all
>  that needs to be done is gather a list of all tickets closed before
>  the branch, no more of the digging through thousands of commit
>  messages crap.
>  
Those things should line up to create development plan, and each such 
issue would be tied to a specific version number. Then planning the next 
release, the beta switch, the 1.0 release would come out naturally, 
without hot debates.

That's what I am telling since the moment I started pushing the change 
to JIRA.


Regards,
Aleksey Bragin