[Gvsig_english] Solution time.

[Francisco José Peñarrubia]

Hi all.

I want to point out 2 things related to this.

One: The lists are maintained by the community and surveyed by testers 
and people from gvSIG projects. But the most important part is 
"community". There is no obligation to answer questions or anything 
else, people here is answering questions in his free time, or in time 
that his company allow them to answer questions. If a solution comes 
quickly (and right, because sometimes it maybe a poor solution), then 
"kudos" to the people answering, and thanks from the whole commuty. 
Besides that, if someone needs better support, there is professional 
support that he can contract with any of the companies involved in this 
project.

Two: If a new bug comes, there are people that will read the bug, and 
decide IF this bug will be fixed for next release or not, depending on 
the complexity and critical level of the bug. It the group that decides 
this issue agree, then, a developer will be assigned. That means IF 
someone is assigned to your ticket, then, the ticket will be solved in 
next release. That said, the people involved in this decission is out 
now. They are in Venezuela, in II Jornadas gvSIG Latinoamericanas, so... 
more time.

I think this is something we can improve, we can add a new state to a 
bug in order to let the people know that a bug is been studied.... but 
maybe for next release. 1.10 is in stabilization period, and new 
processes and bugs are difficult to put (because then, the release will 
never come).

BTW: 1.10 will come because some companies decided to solve some 
annoying bugs. gvSIG team opened a period where every company could 
contribute the bugs that they were willing to fix, and most of this bugs 
are already solved (thanks also to some contributors like Flavio, (M 
support in shape files), many bugs fixed by Ben, or people in Iver, 
Prodevelop or Scolab). New bugs are being considered, but will be 
difficult to solve for this release (but I'm not deciding on this, is 
just an opinion).

So, to finalize, thanks to all people in the list, keep contributing!!

Best regards.

Fran.

Flavio Pompermaier escribió:
> So..bug tracker is less mantained maybe..?
> I opened three tickets on the 21/06 (#14395, #14396 and #14397) but up
> to now they are still unassigned..
> Just for one of the two i received a comment two days after its
> opening ("Have you tested this using the new version (1.10) that is
> under development?"), but nothing else..
>
> Why are tickets (which are more important IMHO) less observed than the
> topics on the mailing list??
>
> Best regards,
> Flavio
>
> 2010/7/12 Enrique Lorenzo Herrero <lorheren at itacyl.es>:
>   
>> It's amazing how quickly you can find solutions on this list! Thanks to gvSIG team and gvSIG community!
>>
>> An example:
>>
>> Fri Jul 9 13:40:29 CEST 2010:
>> Rolf Annecke asks for a solution for a really big problem: his project doesn't work.
>>
>> Fri Jul 9 13:55:06 CEST 2010 (15 minutes later):
>> First suggestions by Benjamin Ducke
>>
>> Fri Jul 9 14:47:46 CEST 2010 (67 minutes later):
>> Solution provided by Vicente Caballero
>>
>> Fri Jul 9 16:10:33 CEST 2010 (150 minutes later):
>> Rolf confirms the solution
>>
>> I have to measure time in minutes. Great!
>>
>> Enrique Lorenzo Herrero
>> INSTITUTO TECNOLÓGICO AGRARIO
>> Junta de Castilla y León
>> Valladolid
>> España
>> _______________________________________________
>> Gvsig_internacional mailing list
>> Gvsig_internacional at listserv.gva.es
>> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>>
>>     
> _______________________________________________
> Gvsig_internacional mailing list
> Gvsig_internacional at listserv.gva.es
> http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional
>   

-- 
Fran Peñarrubia
Scolab
www.scolab.es

Asociación gvSIG
www.gvsig.com