Great, thanks Alex. I see a minor issue: users who are not aware of the Processing tracker will probably open tickets in the main tracker with the general category Processing/Sextante and won't be able to specify which is the affected backend (the Processing bug tracker has a subcategory for each backend: SAGA GIS, GRASS GIS etc).
A possible workaround would be to replace the category Processing/Sextante with Processing/SAGA GIS, Processing/R, Processing GRASS GIS etc. Thanks Regards On Wed, Mar 26, 2014 at 9:31 AM, Alexander Bruy <alexander.b...@gmail.com>wrote: > Hi all, > > thanks to Alex, now Processing/SEXTANTE bugtracker is > a subproject of QGIS. All Processing tickets should be visible > inside main QGIS tracker, but for submitting issue one should > use Processing tracker. > > Please test. If this solution will not work fine for us we can always > restore previous state. > > 2014-03-25 17:08 GMT+02:00 Alexander Bruy <alexander.b...@gmail.com>: > > +1 from me to make Processing/SEXTANTE subproject if > > this keep all tickets categories and allow to see Processing > > bugs among QGIS ones > > > > 2014-03-24 21:32 GMT+02:00 Alex Mandel <tech_...@wildintellect.com>: > >> As a sub-project, it would show up in queries of the main QGIS ticket > >> system, but at the same time be able to have it's own internal > categories. > >> > >> This to me seems the best compromise. It's really a big plugin with a > >> myriad of backends. That complexity is what makes it a little different > >> from the others mentioned. The others mentioned could be sub-projects of > >> the main QGIS too. In reality all of them are core plugins, but they are > >> still plugins. None of them are required to make QGIS work (boot). Hence > >> they each have their own category. The challenge here is > >> Processing/Sextante(I always call it by both since I do the the > >> possibility of Processing stuff that isn't sextante) needs it's own > >> categories/sub-categories. > >> > >> Also it's really easy for use to try moving it to be a subproject and > >> then reassess (Takes about 30 seconds to move it). If it's still not > >> right then we can talk about how to move tickets. > >> > >> Thanks, > >> Alex > >> > >> On 03/24/2014 12:05 PM, Filipe Dias wrote: > >>> Hi > >>> I think Processing tickets should be in the main bug tracker, since > GDAL > >>> tools, fTools and Grass plugin tickets are also there. > >>> > >>> Also, Qgis-Processing is a really big (and great) feature, that > interests a > >>> lot of users, so it makes sense to keep its tickets in the main > tracker. > >>> > >>> Regards > >>> F. > >>> > >>> > >>> On Mon, Mar 24, 2014 at 6:02 PM, Alex Mandel < > tech_...@wildintellect.com>wrote: > >>> > >>>> On 03/24/2014 05:10 AM, Filipe Dias wrote: > >>>>> Hi > >>>>> > >>>>> QGIS-Processing (former Sextante) has open tickets on two > bugtrackers: > >>>>> > >>>>> - the plugin bug tracker, built when it was a plugin, but with a lot > of > >>>>> active tickets -> http://hub.qgis.org/projects/sextante/activity > >>>>> > >>>>> - the main bug tracker with a few open tickets -> > >>>>> http://hub.qgis.org/projects/quantum-gis/issues > >>>>> > >>>>> I understand those two can't be merged in one go, because the > >>>>> plugin-bugtracker has categories (QGIS-Processing SAGA GIS, > >>>> QGIS-Processing > >>>>> GRASS GIS etc) that don't fit in the main bug tracker. But this > should be > >>>>> solved ASAP, because the current situation is quite confusing > >>>>> > >>>>> Regards > >>>>> F. > >>>>> > >>>>> > >>>> > >>>> I'm of the opinion that the tracker should continue to be the Plugin > >>>> tracker, not the main QGIS tracker. So I'd propse moving any > >>>> Sextante/Processing tickets from the main or linking them into the > >>>> Plugin tracker. > >>>> > >>>> To me it's still a plugin, just a core plugin but big enough that it's > >>>> really a subproject. If we wanted to move the Plugin tracker as a > >>>> sub-project of QGIS that would also make sense. > >>>> > >>>> Also Processing bugs aside from Processing not loading aren't > >>>> showstoppers for release. > >>>> > >>>> Thanks, > >>>> Alex > >>>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> 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 > > > > > > > > -- > > Alexander Bruy > > > > -- > Alexander Bruy > _______________________________________________ > 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