[Qgis-developer] When is 2.2 really due?

2014-02-21 Thread Andreas Neumann
Hi,

Maybe I did not follow all discussion. But I see people posting tweets
and blogs everywhere that QGIS 2.2 will be available in 24h or something
similar.

Is this really true? Don't we require a couple of days for packaging,
testing that the binaries really work, etc.?

I am just a bit worried that people put out false promises and increased
pressure on the release manager, making people believe that they can
install QGIS 2.2. Monday morning ...

Sorry if I don't know all the details - this is more a question than a
comment as I am not totally aware of what tasks are required to do the
releases.

Andreas
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] When is 2.2 really due?

2014-02-21 Thread Sandro Santilli
On Fri, Feb 21, 2014 at 12:17:23PM +, Andreas Neumann wrote:
 Hi,
 
 Maybe I did not follow all discussion. But I see people posting tweets
 and blogs everywhere that QGIS 2.2 will be available in 24h or something
 similar.
 
 Is this really true? Don't we require a couple of days for packaging,
 testing that the binaries really work, etc.?
 
 I am just a bit worried that people put out false promises and increased
 pressure on the release manager, making people believe that they can
 install QGIS 2.2. Monday morning ...

Well, I think it's a matter of perception.

It would take a simple git tag for me to be able to install QGIS 2.2.0.
For somebody else it'd take a .deb or .rpm or .exe package instead.

The way I see it, a release should be considered published as soon
as a versioned tarball with the source code is made available somewhere
on the internet.

It may be a good habit, in the future, to tag release candidates
for packagers to test them before going final.

--strk;

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] When is 2.2 really due?

2014-02-21 Thread Jürgen E . Fischer
Hi Andreas,

On Fri, 21. Feb 2014 at 12:17:23 +, Andreas Neumann wrote:
 Maybe I did not follow all discussion. But I see people posting tweets and
 blogs everywhere that QGIS 2.2 will be available in 24h or something similar.

 Is this really true? Don't we require a couple of days for packaging, testing
 that the binaries really work, etc.?

Yes.  That's what we had the freeze period for.  But we're going to release
only the sources today (which still lasts 18h in Alaska) and call for packages
after that.

 I am just a bit worried that people put out false promises and increased
 pressure on the release manager, making people believe that they can install
 QGIS 2.2. Monday morning ...

The release manager is blocking people from continuing their bug fixing work
after having blocked them to doing their feature work already.

Releasing just the sources on the release date will probably just put pressure
on the packagers to get packages out asap.  But there's no set date when that
needs to happen.  But Monday is hopefully not far off.


Jürgen

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden   http://www.norbit.de
QGIS PSC member (RM)  Germany  IRC: jef on FreeNode 


-- 
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] When is 2.2 really due?

2014-02-21 Thread Andreas Neumann
Hi Jürgen,

Thanks for the clarification.

Maybe in the future we could also test binary packages before we
officially release QGIS. After all this is what people use out their.
If packages are broken (even if QGIS from source is fine) this will be
bad for QGIS reputation. 95% of the QGIS users will judge QGIS after the
quality of the package they install. They would not install from source.

I guess any company with a product would do that. I know, we are a
project and not a company, but I think from a QA perspective we should
really also test packages before releasing stuff. At least for the most
common OS, like Win64, latest OSX, latest Ubuntu/Debian.

Anyway - thanks for all the work to all the devs and to you as release
manager!

Andreas

Am 21.02.2014 15:17, schrieb Jürgen E. Fischer:
 Hi Andreas,
 
 On Fri, 21. Feb 2014 at 12:17:23 +, Andreas Neumann wrote:
 Maybe I did not follow all discussion. But I see people posting tweets and
 blogs everywhere that QGIS 2.2 will be available in 24h or something similar.
 
 Is this really true? Don't we require a couple of days for packaging, testing
 that the binaries really work, etc.?
 
 Yes.  That's what we had the freeze period for.  But we're going to release
 only the sources today (which still lasts 18h in Alaska) and call for packages
 after that.
 
 I am just a bit worried that people put out false promises and increased
 pressure on the release manager, making people believe that they can install
 QGIS 2.2. Monday morning ...
 
 The release manager is blocking people from continuing their bug fixing work
 after having blocked them to doing their feature work already.
 
 Releasing just the sources on the release date will probably just put pressure
 on the packagers to get packages out asap.  But there's no set date when that
 needs to happen.  But Monday is hopefully not far off.
 
 
 Jürgen
 

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] When is 2.2 really due?

2014-02-21 Thread Jürgen E . Fischer
Hi Andreas,

On Fri, 21. Feb 2014 at 15:30:45 +, Andreas Neumann wrote:
 Maybe in the future we could also test binary packages before we
 officially release QGIS. After all this is what people use out their.
 If packages are broken (even if QGIS from source is fine) this will be
 bad for QGIS reputation. 95% of the QGIS users will judge QGIS after the
 quality of the package they install. They would not install from source.

That's what the test period is for - the differences there are minor (at least
for Windows and the debian/ubuntu packages).

But a lot of people will always wait for the release before they start to test
and find stuff that no one ran into while testing - of course some of those
could be found in a separate package testing phase (and with a extensive test
suite), but packaging problems can also be handled outside of the qgis release
schedule.

 I guess any company with a product would do that. I know, we are a project
 and not a company, but I think from a QA perspective we should really also
 test packages before releasing stuff. At least for the most common OS, like
 Win64, latest OSX, latest Ubuntu/Debian.

As the packaging is now outside of qgis (and IMHO is was that way earlier - eg.
bugs in the OSGeo4W packages should be filed there - but the standalone
installer from repackaged OSGeo4W packages is a gray area).

For Windows there's already some threshold - I'll first put the new release
into OSGeo4W and produce a standalone installer some time later...


Jürgen

-- 
Jürgen E. Fischer norBIT GmbH   Tel. +49-4931-918175-31
Dipl.-Inf. (FH)   Rheinstraße 13Fax. +49-4931-918175-50
Software Engineer D-26506 Norden   http://www.norbit.de
QGIS PSC member (RM)  Germany  IRC: jef on FreeNode 


-- 
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Jelto Buurman, HR: Amtsgericht Emden, HRB 5502

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer


Re: [Qgis-developer] When is 2.2 really due?

2014-02-21 Thread Sandro Santilli
On Fri, Feb 21, 2014 at 05:13:59PM +0100, Jürgen E. Fischer wrote:

 But a lot of people will always wait for the release before they start to test
 and find stuff that no one ran into while testing - of course some of those
 could be found in a separate package testing phase (and with a extensive test
 suite), but packaging problems can also be handled outside of the qgis release
 schedule.

That's why maintaining a stable branch is important: there'll always
be a lot more testing after a release is out. You can't beat thousand
of users with any automated tests... :)

--strk;

 ()  ASCII ribbon campaign  --  Keep it simple !
 /\  http://strk.keybit.net/rants/ascii_mails.txt  
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer