Hi,

I'd like to remind everyone that the 2.7 development cycle ended at 12:00
UTC. We are now in feature freeze on the road to the 2.8 release on 2015-02-20
http://www.timeanddate.com/countdown/generic?p0=1440&iso=20150220T12&year=2015&month=02&day=20&hour=12&min=0&sec=0&msg=2.8%20Release
(27 days away; see also roadmap
<http://qgis.org/en/site/getinvolved/development/index#road-map.html>).

Now *we*, *the community*, need to prepare QGIS for release. No new features
will be added anymore. *Users*, if not already begun, should now start
extensive testing of master and report bugs on the hub <http://hub.qgis.org>.
*Developers* should move their focus from creating new features to fixing bugs.
*Translators* can can continue their work (we maintain all our translations on
transifex now).

The nightly builds of QGIS testing available for Windows
<http://www.qgis.org/en/site/forusers/alldownloads.html#windows>, Linux (Debian
<http://www.qgis.org/en/site/forusers/alldownloads.html#id3> and Ubuntu
<http://www.qgis.org/en/site/forusers/alldownloads.html#qgis-testing>) and Mac
OS <http://www.qgis.org/en/site/forusers/alldownloads.html#id13> are now
effectively snapshots of what's going to be released.  Except of course for the
bugs that are going to be fixed until release day.  For Windows there will also
be weekly release candidates of the standalone installer
<http://www.qgis.org/downloads/weekly/>.

Lets keep up working together to make 2.8 another great release.


Jürgen

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

Attachment: signature.asc
Description: Digital signature

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

Reply via email to