[EnMasse] Changelog for releases

[Paolo Patierno]

Yes sure ! I only meant to add milestone to the issue in systemtests but
not adding it to the changelog.

On 25 May 2017 08:03, "Ulf Lilleengen" <lulf at redhat.com> wrote:

> My take is that in retrospect knowing that a feature was tested on a
> particular version could be useful, particularity when debugging and doing
> post mortems on production issues. But probably not something to put in the
> changelog.
>
> Ulf
>
> On May 25, 2017 07:36, "Paolo Patierno" <ppatiern at redhat.com> wrote:
>
> It sounds good to me as well !
>
> Do we have to do the same even for systemtests issues so not real new
> feature ? I.e. opening an issue for planning a new MQTT integration test
> and set it to the coming milestone ?
>
>
> On 23 May 2017 13:04, "Gordon Sim" <gsim at redhat.com> wrote:
>
> On 23/05/17 09:40, Ulf Lilleengen wrote:
>
>> Hi,
>>
>> I've started to maintain a changelog[1] so that we can keep track of
>> what ends up in different releases of EnMasse.
>>
>> To make that job easier, I propose a simple guideline that doesn't cost
>> much in terms of developer effort: whenever you work on a github issue
>> and resolve it, set the milestone to the _next_ release version of
>> EnMasse [2]
>>
>> The next version is likely to be 0.(N+1).0 for some time, and then we
>> can revisit this when we need to think about major releases or if this
>> approach doesn't work.
>>
>> wdyt?
>>
>
> Sounds good to me!
>
>
> _______________________________________________
> enmasse mailing list
> enmasse at redhat.com
> https://www.redhat.com/mailman/listinfo/enmasse
>
>
>
> _______________________________________________
> enmasse mailing list
> enmasse at redhat.com
> https://www.redhat.com/mailman/listinfo/enmasse
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/enmasse/attachments/20170525/93972da1/attachment.htm>