Hi All Just a correction:
> Source tarballs can be obtained from here: > > http://qgis.org/downloads/qgis-1.7.0.tar.bz2 > http://qgis.org/downloads/qgis-1.7.0.tar.bz2.md5 Should have read: Source tarballs can be obtained from here: http://qgis.org/downloads/qgis-1.7.0.tar.gz http://qgis.org/downloads/qgis-1.7.0.tar.gz.md5 Regards Tim On Sun, Jun 5, 2011 at 11:44 PM, Tim Sutton <[email protected]> wrote: > Dear QGIS devs & packagers > > --- Note to casual readers --- > > Please do not pre-announce this release - give the packagers and > release team a chance to do their thing so that people hearing about > the release have a fair chance of finding a package, reading all our > press material etc. > > --- End note --- > > I have tagged QGIS 1.7.0 for release. The branch can be checked out > from git (QGIS official repo) on tag: > > git checkout final-1_7_0 > > You may need to do a git fetch on the repo first before the tag is > available to you e.g. > > git fetch qgis-upstream > git checkout final-1_7_0 > > Source tarballs can be obtained from here: > > http://qgis.org/downloads/qgis-1.7.0.tar.bz2 > http://qgis.org/downloads/qgis-1.7.0.tar.bz2.md5 > > > It is my intention to maintain the 1.7.0 branch (probably I should > rename it to release-1_7) to backport bugfixes so that we can put out > 1.7.x maintenance releases in the run up to the creation of 2.0. If > you are working in master and fix a bug, if you could be so kind as to > cherry-pick your commit into the 1.7 branch and push it over to the > main repo. > > > If you make a package please be so kind as to update the download wiki > page at http://www.qgis.org/wiki/Download with the details of your > package. > > If you are able to make packages for unlisted platforms / distros > please let me know so that we can avoid duplication of effort. > > I would like to make the release announcement next week, so it will be > great to have as many packages as possible ready by then. > > GIT master is open again for general commits - please seek guidance > from Marco Hugentobler (PSC Code Manager) if you are planning any > major code changes. > > Obviously there is a lot of new stuff going on with GIT and Redmine, > so if packagers have particular issues we may need to adjust the > workflow. Please feel free to discuss on the thread started by this > email. > > > Many thanks to all the developers, testers, bug fixers, bug reporters, > document writers, translators and users that help to make QGIS a > reality. > > Lastly can I call on the release team to put together visual > changelog, press announcements etc. ready for the release date? I will > send you an email when the packages are ready and you can start > broadcasting announcements. > > Best regards > > > -- > Tim Sutton - QGIS Project Steering Committee Member (Release Manager) > ============================================== > Please do not email me off-list with technical > support questions. Using the lists will gain > more exposure for your issues and the knowledge > surrounding your issue will be shared with all. > > Visit http://linfiniti.com to find out about: > * QGIS programming and support services > * Mapserver and PostGIS based hosting plans > * FOSS Consulting Services > Skype: timlinux > Irc: timlinux on #qgis at freenode.net > ============================================== > -- Tim Sutton - QGIS Project Steering Committee Member (Release Manager) ============================================== Please do not email me off-list with technical support questions. Using the lists will gain more exposure for your issues and the knowledge surrounding your issue will be shared with all. Visit http://linfiniti.com to find out about: * QGIS programming and support services * Mapserver and PostGIS based hosting plans * FOSS Consulting Services Skype: timlinux Irc: timlinux on #qgis at freenode.net ============================================== _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
