[Gvsig_english] GvSIG 1.9 bug hunt?

Mon May 18 09:12:58 CEST 2009

Benjamin Ducke escribió:
>>> Do I understand right that 1.9 is basically a continuation
>>> of the 1.X code base, whereas 2.0 will be based on the
>>> refactored code?
>>
>> Yes, that's right.
>>
>>   César
>>
> 
> In that case: how about organizing a community bug hunt
> at some point before 1.9 gets released?
> Maybe a month or so before the release, all users could
> download the same set of sample data (e.g. I'd have some fairly
> rich dataset from North Carolina available) and start intensively
> testing all functionality they are interested in on that same
> data. That should make reproducing problems easy.
> 
> I am talking bug hunting only, no feature requests.
> 
> Ben
> 

We will probably release a beta version very soon, and it would be a 
good idea to focus the bug hunting on that version.

Our testing team is preparing something to coordinate the testing 
efforts, so I think they will suggest some guidelines and data to use.

By the way, I'm pretty sure you are able to find more bugs than we are 
able to fix... but we'll squeeze the biggest ones at least.

Best regards,

   César

> 
>>> Thanks,
>>>
>>> Ben
>>>
>>>
>>> ----- Original Message -----
>>> From: "César Martínez Izquierdo" <cesar.izq at gmail.com>
>>> To: "Users and Developers mailing list" 
>>> <gvsig_internacional at runas.cap.gva.es>
>>> Sent: Thursday, May 14, 2009 3:17:26 PM GMT +01:00 Amsterdam / Berlin 
>>> / Bern / Rome / Stockholm / Vienna
>>> Subject: Re: [Gvsig_english] Severe editing issue in GvSIG 1.1.2
>>>
>>> Benjamin Ducke escribió:
>>>> Hello all,
>>>>
>>>> unfortunately, the problem is slightly more complex than that and
>>>> affects editing when interacting with the CAD editor view to select
>>>> features.
>>>>
>>>> The bugs and some work-arounds are documented on our gvSIG support
>>>> pages:
>>>>
>>>> http://www.oadigital.net/software/gvsigoade/gvsigbugs/62
>>>>
>>>> Best,
>>>>
>>>> Ben
>>> Hello again,
>>>
>>> As you probably know, we are currently working both in 1.9 and 2.0
>>> versions, and we hope to release 1.9 soon. Therefore, I doubt we wish to
>>> spend resources in 1.1.2 version at this time (this is a personal 
>>> opinion).
>>>
>>> If you are in a hurry, fixing bugs in gvSIG TRUNK will make 1.9 version
>>> to release earliear.
>>>
>>> Best regards,
>>>
>>>   César
>>>
>>>
>>>
>>>> Cesar Martinez Izquierdo wrote:
>>>>> Hello Jo,
>>>>>
>>>>> I think there is another work-around: press ENTER after typing the
>>>>> wished value. I hope this is good enough for you.
>>>>>
>>>>> Regards,
>>>>>
>>>>>   César
>>>>>
>>>>>
>>>>>
>>>>> Joanne Cook escribió:
>>>>>> Dear List,
>>>>>>
>>>>>> We have just come across a severe bug in editing attribute data in
>>>>>> GvSIG 1.1.2. To reproduce this issue:
>>>>>>
>>>>>> 1) Load a shape file (I used a polygon shape file)
>>>>>> 2) Start editing it, select a feature using the standard selector (so
>>>>>> it goes yellow)
>>>>>> 3) Open the attribute table and choose to move selected features to
>>>>>> the top
>>>>>> 4) Change a value in the attributes for the selected feature
>>>>>> 5) Either use the cursor to move to a different value in the table,
>>>>>> or select a different feature in your view WITHOUT SAVING YOUR 
>>>>>> CHANGES
>>>>>> 6) You should find that the value of the attribute you edited gets
>>>>>> carried over to the new feature, over-writing whatever value was
>>>>>> there before.
>>>>>>
>>>>>> The only work-around we have found seems to be to save the changes
>>>>>> after every edit, but this involves stopping editing, agreeing to
>>>>>> save changes, then starting editing again, which is very 
>>>>>> time-consuming.
>>>>>>
>>>>>> This has been reproduced on several different pcs running windows and
>>>>>> linux, and versions 1.1.1 and 1.1.2. However it does not appear in 
>>>>>> 1.9.
>>>>>>
>>>>>> I understand that all development work is now focussed on 1.9 and 2,
>>>>>> but this is a very severe bug and makes it very hard for us to
>>>>>> currently recommend using GvSIG to either staff or clients, at a time
>>>>>> when we are trying to do just that. As it has been fixed in 1.9, is
>>>>>> there any chance of a backport of this fix to 1.1.2?
>>>>>>
>>>>>> Many thanks
>>>>>>
>>>>>> Jo
>>>>>>
>>>>>
>>>>
>>>
>>> -- 
>>> César Martínez Izquierdo
>>> Equipo de desarrollo gvSIG
>>> http://www.gvsig.org/web/
>>>
>>> IVER T.I.
>>> C/ Lérida, 20
>>> 46009 Valencia - Spain
>>> http://www.iver.es
>>> _______________________________________________
>>> Gvsig_internacional mailing list
>>> Gvsig_internacional at runas.cap.gva.es
>>> http://runas.cap.gva.es/mailman/listinfo/gvsig_internacional
>>>
>>>
>>>
>>> ------
>>> Files attached to this email may be in ISO 26300 format (OASIS Open 
>>> Document Format). If you have difficulty opening them, please visit 
>>> http://iso26300.info for more information.
>>>
>>>
>>> _______________________________________________
>>> Gvsig_internacional mailing list
>>> Gvsig_internacional at runas.cap.gva.es
>>> http://runas.cap.gva.es/mailman/listinfo/gvsig_internacional
>>
>> _______________________________________________
>> Gvsig_internacional mailing list
>> Gvsig_internacional at runas.cap.gva.es
>> http://runas.cap.gva.es/mailman/listinfo/gvsig_internacional
>>
>>
> 
> 

-- 
César Martínez Izquierdo
Equipo de desarrollo gvSIG
http://www.gvsig.org/web/

IVER T.I.
C/ Lérida, 20
46009 Valencia - Spain
http://www.iver.es