Re: [GRASS-PSC] [GRASS-dev] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 <- ? -> 7.0]
Hi, 2013/3/19 Sören Gebbert : > It seems to be a good idea. > However, i have to apply the 3D raster patch[1] then as soon as > possible to get the voxel stuff working with large data. But this will > bring the risk of losing backward compatibility . Patch that removes the buggy LRE compression has been applied to trunk #55462. Tests for 3D raster modules and the library passed successfully. The patch should assure backward compatibility. I hope i did not break anything. :) Best regards Soeren > > Please exclude the temporal GIS stuff in the tech-preview 7.0 release, > since so many manual pages are still missing. > > Best > Soeren > > [1] http://trac.osgeo.org/grass/ticket/1752 > > 2013/3/19 Markus Neteler : >> On Tue, Mar 19, 2013 at 7:55 PM, Markus Metz >> wrote: >>> I like the idea of a tech-preview release of GRASS7! >> >> Me, too. >> >>> I think that no more (or at least not many) major changes will go into >>> GRASS 7, apart from the wxGUI code base. >> >> We should also remember that this will go towards 7.0 and then a >> nice 7.1 and so forth are expecting us. >> >> (At the FOSS4G Lausanne 2006 we even had a "GRASS 8" (grassotto, >> Italian word joke) logo :-) - maybe I can get the file from Alessandro >> Frigeri >> who draw it.) >> >>> Therefore it would IMHO be >>> very beneficial to get more feedback on GRASS 7 in order to detect and >>> fix remaining bugs. >>> >>> I also like your proposed release schedule of max 1-2 weeks. >> >> If you accept me to manage the release and related stuff, I am happy >> to prepare things as needed with your help. >> >> markusN >> >> PS: Who cannot resist: >> >> http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=type&order=priority&priority=blocker&priority=critical&col=id&col=summary&col=milestone&col=priority&col=status&col=owner&col=component&milestone=7.0.0 >> ___ >> grass-dev mailing list >> grass-...@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] [GRASS-dev] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 <- ? -> 7.0]
On Tue, Mar 19, 2013 at 9:32 PM, Sören Gebbert wrote: > Please exclude the temporal GIS stuff in the tech-preview 7.0 release, > since so many manual pages are still missing. This reason is too weak :) I think that excluding it is way more work that writing draft manual pages. I can assist with that (we can discuss offlist). Markus ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] [GRASS-dev] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 <- ? -> 7.0]
2013/3/19 Markus Metz : > I like the idea of a tech-preview release of GRASS7! > +1 > I think that no more (or at least not many) major changes will go into > GRASS 7, apart from the wxGUI code base. Therefore it would IMHO be > very beneficial to get more feedback on GRASS 7 in order to detect and > fix remaining bugs. > Also in pygrass there is "some" work to do yet > > Markus M > -- ciao Luca http://gis.cri.fmach.it/delucchi/ www.lucadelu.org ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] [GRASS-dev] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 <- ? -> 7.0]
Hi, 2013/3/19 Sören Gebbert : > It seems to be a good idea. > However, i have to apply the 3D raster patch[1] then as soon as > possible to get the voxel stuff working with large data. But this will > bring the risk of losing backward compatibility . this will happen time by time... We have two options: 1) start releasing tech-previews later 2) start releasing tech-previews earlier with risk of breaking > Please exclude the temporal GIS stuff in the tech-preview 7.0 release, > since so many manual pages are still missing. Hm, there will be more unstable or non-documented areas in GRASS 7. Excluding them from tech-previewes will be extra work for packagers and the benefit will be debatable. Martin -- Martin Landa * http://geo.fsv.cvut.cz/~landa ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] [GRASS-dev] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 <- ? -> 7.0]
It seems to be a good idea. However, i have to apply the 3D raster patch[1] then as soon as possible to get the voxel stuff working with large data. But this will bring the risk of losing backward compatibility . Please exclude the temporal GIS stuff in the tech-preview 7.0 release, since so many manual pages are still missing. Best Soeren [1] http://trac.osgeo.org/grass/ticket/1752 2013/3/19 Markus Neteler : > On Tue, Mar 19, 2013 at 7:55 PM, Markus Metz > wrote: >> I like the idea of a tech-preview release of GRASS7! > > Me, too. > >> I think that no more (or at least not many) major changes will go into >> GRASS 7, apart from the wxGUI code base. > > We should also remember that this will go towards 7.0 and then a > nice 7.1 and so forth are expecting us. > > (At the FOSS4G Lausanne 2006 we even had a "GRASS 8" (grassotto, > Italian word joke) logo :-) - maybe I can get the file from Alessandro > Frigeri > who draw it.) > >> Therefore it would IMHO be >> very beneficial to get more feedback on GRASS 7 in order to detect and >> fix remaining bugs. >> >> I also like your proposed release schedule of max 1-2 weeks. > > If you accept me to manage the release and related stuff, I am happy > to prepare things as needed with your help. > > markusN > > PS: Who cannot resist: > > http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=type&order=priority&priority=blocker&priority=critical&col=id&col=summary&col=milestone&col=priority&col=status&col=owner&col=component&milestone=7.0.0 > ___ > grass-dev mailing list > grass-...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] [GRASS-dev] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 <- ? -> 7.0]
The 2 biggest issues I've run into teaching with GRASS 7 has been 1) the difficulty of getting a Linux version and 2) the common 'missing dll' problem for Windows. Michael __ C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University Tempe, AZ 85287-2402 USA voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671(SHESC), 480-727-0709 (CSDC) www:http://csdc.asu.edu, http://shesc.asu.edu http://www.public.asu.edu/~cmbarton On Mar 19, 2013, at 12:57 PM, Markus Neteler wrote: > On Tue, Mar 19, 2013 at 7:55 PM, Markus Metz > wrote: >> I like the idea of a tech-preview release of GRASS7! > > Me, too. > >> I think that no more (or at least not many) major changes will go into >> GRASS 7, apart from the wxGUI code base. > > We should also remember that this will go towards 7.0 and then a > nice 7.1 and so forth are expecting us. > > (At the FOSS4G Lausanne 2006 we even had a "GRASS 8" (grassotto, > Italian word joke) logo :-) - maybe I can get the file from Alessandro Frigeri > who draw it.) > >> Therefore it would IMHO be >> very beneficial to get more feedback on GRASS 7 in order to detect and >> fix remaining bugs. >> >> I also like your proposed release schedule of max 1-2 weeks. > > If you accept me to manage the release and related stuff, I am happy > to prepare things as needed with your help. > > markusN > > PS: Who cannot resist: > > http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=type&order=priority&priority=blocker&priority=critical&col=id&col=summary&col=milestone&col=priority&col=status&col=owner&col=component&milestone=7.0.0 > ___ > grass-psc mailing list > grass-psc@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-psc ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] [GRASS-dev] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 <- ? -> 7.0]
On Tue, Mar 19, 2013 at 7:55 PM, Markus Metz wrote: > I like the idea of a tech-preview release of GRASS7! Me, too. > I think that no more (or at least not many) major changes will go into > GRASS 7, apart from the wxGUI code base. We should also remember that this will go towards 7.0 and then a nice 7.1 and so forth are expecting us. (At the FOSS4G Lausanne 2006 we even had a "GRASS 8" (grassotto, Italian word joke) logo :-) - maybe I can get the file from Alessandro Frigeri who draw it.) > Therefore it would IMHO be > very beneficial to get more feedback on GRASS 7 in order to detect and > fix remaining bugs. > > I also like your proposed release schedule of max 1-2 weeks. If you accept me to manage the release and related stuff, I am happy to prepare things as needed with your help. markusN PS: Who cannot resist: http://trac.osgeo.org/grass/query?status=assigned&status=new&status=reopened&group=type&order=priority&priority=blocker&priority=critical&col=id&col=summary&col=milestone&col=priority&col=status&col=owner&col=component&milestone=7.0.0 ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] [GRASS-dev] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 <- ? -> 7.0]
I like the idea of a tech-preview release of GRASS7! I think that no more (or at least not many) major changes will go into GRASS 7, apart from the wxGUI code base. Therefore it would IMHO be very beneficial to get more feedback on GRASS 7 in order to detect and fix remaining bugs. I also like your proposed release schedule of max 1-2 weeks. Markus M On Tue, Mar 19, 2013 at 10:25 AM, Moritz Lennert wrote: > On 18/03/13 23:04, Markus Neteler wrote: >> >> On Fri, Jan 11, 2013 at 9:53 AM, Rainer M Krug wrote: >> ... >>> >>> Following the discussion, I would like to install GRASS 7 weekly >>> snapshot. I relized the "Binary" >>> link (http://grass.osgeo.org/download/software/) but it points back to >>> the Linux Download page, >>> but I could not find any binaries there for GRASS 7? Maybe this link >>> should be removed? >>> >>> Just wondering, but not a problem, as I am going to install from source >>> anyway. >> >> >> In the past days I have cleaned up several of the Web pages. >> I hope they are much clearer now. GRASS 7 downloads are now properly >> mentioned as well. > > > Much clearer now ! > > I would like to take this debate as an opportunity to touch upon the > question of a possible tech-preview release of GRASS7. > > Several reasons for that: > > - More and more people are using it (and we are pushing more and more people > toward using it). Binaries are available for windows and mac, but not for > most Linux distributions. A preview release might make it easier for these > distributions to package grass7 and make it available to a larger audience. > > - In many institutions it is (understandably) not easy to convince > IT-managers to install development snapshots instead of released software. > Having an official release (even if it is only a tech-preview release) > should make it easier to install grass7 in institutional settings. > > - I think that grass7 is in a form where we can start advertising it more > widely and more officially. In terms of timing, it would be great to be able > to get this out before FOSS4G. > > - From my own egotistical viewpoint, I would love to be able to use grass7 > in my classes next school year, and having a release would make it much > easier for me to do that. > > Concretely, I see the following type of procedure to make it possible: > > - Freeze the svn repository for any direct new commits for a short period > (I'd say max 1-2 weeks). Only a few "release managers" should still have > direct commit access at this point. (Another way to do it would be to keep > commit rights open to anyone, and the role of the release managers would be > to control all commits and revert those that aren't simple bug fixes during > the freeze). > > - Publish the state of the code at the beginning of the freeze as RC1 with a > wide call for testing. > > - Only bug fix* commits. > > - Publish RC2 after some bug fixing (possibly after one week). > > - Continue bug fixing*. > > - Release tech-preview (possibly at the end of week 2) with a huge > disclaimer that this is a tech-preview release and not considered final and > stable. > > - Open repository again for more general development. > > > I don't think we should create a release branch as this would just be a > tech-preview snaphot of the ongoing development. > > This obviously implies that we plan ahead and that all developers know when > this freeze will happen, thus avoiding to commit any large and fundamental > changes just before the freeze. And that we all put aside time during that > freeze for testing and bug fixing. > > What do you think ? > > Moritz > ___ > grass-dev mailing list > grass-...@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
Re: [GRASS-PSC] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 <- ? -> 7.0]
I think this is a good idea. At the moment, GRASS 7 seems stable and everything or almost everything is working for Mac. There are a few issues, but not major ones. One thing I remember is a problem with the display of north arrows. Volume display is still unstable, but that is a problem with both ver. 6 and 7. Michael __ C. Michael Barton Director, Center for Social Dynamics & Complexity Professor of Anthropology, School of Human Evolution & Social Change Arizona State University Tempe, AZ 85287-2402 USA voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) fax: 480-965-7671(SHESC), 480-727-0709 (CSDC) www:http://csdc.asu.edu, http://shesc.asu.edu http://www.public.asu.edu/~cmbarton On Mar 19, 2013, at 2:25 AM, Moritz Lennert wrote: > On 18/03/13 23:04, Markus Neteler wrote: >> On Fri, Jan 11, 2013 at 9:53 AM, Rainer M Krug wrote: >> ... >>> Following the discussion, I would like to install GRASS 7 weekly snapshot. >>> I relized the "Binary" >>> link (http://grass.osgeo.org/download/software/) but it points back to the >>> Linux Download page, >>> but I could not find any binaries there for GRASS 7? Maybe this link should >>> be removed? >>> >>> Just wondering, but not a problem, as I am going to install from source >>> anyway. >> >> In the past days I have cleaned up several of the Web pages. >> I hope they are much clearer now. GRASS 7 downloads are now properly >> mentioned as well. > > Much clearer now ! > > I would like to take this debate as an opportunity to touch upon the question > of a possible tech-preview release of GRASS7. > > Several reasons for that: > > - More and more people are using it (and we are pushing more and more people > toward using it). Binaries are available for windows and mac, but not for > most Linux distributions. A preview release might make it easier for these > distributions to package grass7 and make it available to a larger audience. > > - In many institutions it is (understandably) not easy to convince > IT-managers to install development snapshots instead of released software. > Having an official release (even if it is only a tech-preview release) should > make it easier to install grass7 in institutional settings. > > - I think that grass7 is in a form where we can start advertising it more > widely and more officially. In terms of timing, it would be great to be able > to get this out before FOSS4G. > > - From my own egotistical viewpoint, I would love to be able to use grass7 in > my classes next school year, and having a release would make it much easier > for me to do that. > > Concretely, I see the following type of procedure to make it possible: > > - Freeze the svn repository for any direct new commits for a short period > (I'd say max 1-2 weeks). Only a few "release managers" should still have > direct commit access at this point. (Another way to do it would be to keep > commit rights open to anyone, and the role of the release managers would be > to control all commits and revert those that aren't simple bug fixes during > the freeze). > > - Publish the state of the code at the beginning of the freeze as RC1 with a > wide call for testing. > > - Only bug fix* commits. > > - Publish RC2 after some bug fixing (possibly after one week). > > - Continue bug fixing*. > > - Release tech-preview (possibly at the end of week 2) with a huge disclaimer > that this is a tech-preview release and not considered final and stable. > > - Open repository again for more general development. > > > I don't think we should create a release branch as this would just be a > tech-preview snaphot of the ongoing development. > > This obviously implies that we plan ahead and that all developers know when > this freeze will happen, thus avoiding to commit any large and fundamental > changes just before the freeze. And that we all put aside time during that > freeze for testing and bug fixing. > > What do you think ? > > Moritz > ___ > grass-psc mailing list > grass-psc@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-psc ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
[GRASS-PSC] Grass7 tech-preview release [was Re: [GRASS-user] to move or not move ? grass64 <- ? -> 7.0]
On 18/03/13 23:04, Markus Neteler wrote: On Fri, Jan 11, 2013 at 9:53 AM, Rainer M Krug wrote: ... Following the discussion, I would like to install GRASS 7 weekly snapshot. I relized the "Binary" link (http://grass.osgeo.org/download/software/) but it points back to the Linux Download page, but I could not find any binaries there for GRASS 7? Maybe this link should be removed? Just wondering, but not a problem, as I am going to install from source anyway. In the past days I have cleaned up several of the Web pages. I hope they are much clearer now. GRASS 7 downloads are now properly mentioned as well. Much clearer now ! I would like to take this debate as an opportunity to touch upon the question of a possible tech-preview release of GRASS7. Several reasons for that: - More and more people are using it (and we are pushing more and more people toward using it). Binaries are available for windows and mac, but not for most Linux distributions. A preview release might make it easier for these distributions to package grass7 and make it available to a larger audience. - In many institutions it is (understandably) not easy to convince IT-managers to install development snapshots instead of released software. Having an official release (even if it is only a tech-preview release) should make it easier to install grass7 in institutional settings. - I think that grass7 is in a form where we can start advertising it more widely and more officially. In terms of timing, it would be great to be able to get this out before FOSS4G. - From my own egotistical viewpoint, I would love to be able to use grass7 in my classes next school year, and having a release would make it much easier for me to do that. Concretely, I see the following type of procedure to make it possible: - Freeze the svn repository for any direct new commits for a short period (I'd say max 1-2 weeks). Only a few "release managers" should still have direct commit access at this point. (Another way to do it would be to keep commit rights open to anyone, and the role of the release managers would be to control all commits and revert those that aren't simple bug fixes during the freeze). - Publish the state of the code at the beginning of the freeze as RC1 with a wide call for testing. - Only bug fix* commits. - Publish RC2 after some bug fixing (possibly after one week). - Continue bug fixing*. - Release tech-preview (possibly at the end of week 2) with a huge disclaimer that this is a tech-preview release and not considered final and stable. - Open repository again for more general development. I don't think we should create a release branch as this would just be a tech-preview snaphot of the ongoing development. This obviously implies that we plan ahead and that all developers know when this freeze will happen, thus avoiding to commit any large and fundamental changes just before the freeze. And that we all put aside time during that freeze for testing and bug fixing. What do you think ? Moritz ___ grass-psc mailing list grass-psc@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-psc
