Probably the keypoint of this discussion are the different point of views on what the dev community consider the final point of a development cycle. Some consider it the source ball and the packaging a plus. Others include the packages themselves (in their mindset).
I don't want to open a discussion on this but I think that a project like QGIS, which is extending its user base, cannot consider that the majority of its users even don't know how a software is made. And I don't blame them, as I don't know the intricacies of the smartphone I'm writing on right know. If the problem is convincing people to donate to support the complete lifecycle of the project well, this is a different point, but I don't think we will get there hoping they understand what's under the job of releasing a ready to go package... giovanni Il 27/giu/2014 08:45 "Nyall Dawson" <nyall.daw...@gmail.com> ha scritto: > > On 27/06/2014 4:35 pm, "Denis Rouzaud" <denis.rouz...@gmail.com> wrote: > > > > > > For me, a summarize is: save two days of waiting (on a 4+ months > schedule) so <1% users can compile while 99% get frustrated. > > I suspect the actual fraction of users who compile is much much smaller > than this. Maybe 1 in a thousand at most, probably much lower still. > > > > > Why can't we state that release is when windows + mac + ubuntu are ready? > > > > +1 from me. > > Nyall > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer