[Qgis-psc] Visual changelog

[Andreas Neumann]

Hi,

Why don't we plan a reasonable amount of time between the freeze and the 
actual announcement.

One week would be a reasonable time, I think.

This would give packagers a chance to keep up and if there any totally 
severe bugs, they could be addressed.

Visual changelog could be already prepared in advance, ideally. In the 
case of visual changelog, I think it doesn't need money. I just needs 
some coordination - e.g. 3-5 people distribute the work load. Then it 
would only be some 1-2 days of work for each one. For 3.2 release it 
will be less work, because I expect less features than with 3.0

Andreas


On 23.02.2018 13:54, Paolo Cavallini wrote:
> Hi Andreas,
>
> Il 23/02/2018 12:46, Andreas Neumann ha scritto:
>
>> I am not satisfied how the QGIS release process works. Just throwing out
>> a bunch of source code is not how a proper software release should work.
> I understand your concerns; in practice, this would mean:
> * delaying the release until everything is ready
> * allocating more resources to fix what volunteer work could not cover
> for release.
> In additino, I am talking to Giovanni and Matteo, and they already found
> several new issues that should better be fixed before real release.
> Thanks for raising this point.