Visual changelog

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Visual changelog

Andreas Neumann-4
Hi PSC,

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.

For the user, a release is only ready if:

* Binary packages are ready for Windows, OSX and Ubuntu/Debian

* API documentation is finished

* the visual changelog is ready (currently, it is nowhere close to being
ready - will need several man-days of work)

* some concerted effort is being done to announce it on several channels
(with some document as a guideline)

* some plan for documentation is in place

Preannouncing that "QGIS 3 is ready" in such a state will only
disappoint users a lot.

Am I the only one bothered by that fact?

Note that the documentation and the changelog are both areas where
non-dev contributors can help. But apparently, there is no coordinated
effort on both.

Can we do better for future releases?

Thanks,

Andreas

_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
Reply | Threaded
Open this post in threaded view
|

Re: Visual changelog

pcav
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.
--
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html
https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
Reply | Threaded
Open this post in threaded view
|

Re: Visual changelog

Régis Haubourg
In reply to this post by Andreas Neumann-4
Hi Andreas,
I share most concerns and that's why we proposed the "SWOT" meeting to learn experience from that release process.
Let's meet this afternoon!
Regards,
Régis

2018-02-23 13:46 GMT+01:00 Andreas Neumann <[hidden email]>:
Hi PSC,

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.

For the user, a release is only ready if:

* Binary packages are ready for Windows, OSX and Ubuntu/Debian

* API documentation is finished

* the visual changelog is ready (currently, it is nowhere close to being ready - will need several man-days of work)

* some concerted effort is being done to announce it on several channels (with some document as a guideline)

* some plan for documentation is in place

Preannouncing that "QGIS 3 is ready" in such a state will only disappoint users a lot.

Am I the only one bothered by that fact?

Note that the documentation and the changelog are both areas where non-dev contributors can help. But apparently, there is no coordinated effort on both.

Can we do better for future releases?

Thanks,

Andreas

_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc


_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
Reply | Threaded
Open this post in threaded view
|

Re: Visual changelog

Andreas Neumann-4
In reply to this post by pcav
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.

_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc
Reply | Threaded
Open this post in threaded view
|

Re: Visual changelog

Tim Sutton-6
Hi

All good points Andreas. For the visual changelog I have made a few calls for help already - it is a huge work for this release but we didn't get much help on it yet.

I think though there is nothing wrong with messaging ‘our code is frozen, binaries are coming, stand by for the release announcements’ - at least people who follow us see what is coming…

Yes it will be good to chat about in the swot session...

Regards

Tim


On 23 Feb 2018, at 14:58, Andreas Neumann <[hidden email]> wrote:

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.

_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc

 



---

Tim Sutton
QGIS Project Steering Committee Chair





_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc

smime.p7s (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Visual changelog

Anita Graser
In reply to this post by Andreas Neumann-4


On Fri, Feb 23, 2018 at 1:46 PM, Andreas Neumann <[hidden email]> wrote:
Preannouncing that "QGIS 3 is ready" in such a state will only disappoint users a lot.

​At least on Twitter and in the blog.qgis.org post, I made sure that "packages are currently being prepared" is a key part of the message. I hope that users who follow these channels will have the right expectations and won't be disappointed this way. 

Anita



_______________________________________________
Qgis-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/qgis-psc