Re: [Ifolder-dev] Re: Update

2009-06-15 Thread Balakrishnan KalIdas 
Agree with Andrés, we must be creating branches. 

 GG has just tagged the old-UI, just to have a check-point and wanted all 
development to happen in the new UI code, as tremendous effort is being put by 
GG and team along with the HF (Human Factors) for getting this UI. This entire 
UI design has undergone multiple reviews with various users and deployments. If 
we create a branch, then we might lose traction in the new UI code, as the 
older UI will be more stable. GG's idea is to get the new UI stable as early 
and as fast as possible.

 But we are developing some features, then we will have a branch as Andrés 
mentioned. I assume the idea behind the entire process is appreciated and lets 
all help get the new UI stable as fast as possible. Any kind of help is 
appreciated interms of bug reports, comments, critics, etc on the new UI.

Kalis

>>> "GG Hegde"  06/15/09 4:29 PM >>>
Sure we could follow the tagging with the version no. too.
For the newui there was branch created and was merged back to trunk only after 
the development. As this UI has undergone the usability and Human Factor 
guidelines, it would be good to continue with the new one. We shall fix all the 
minor glitches if we have any.
 
thanks and regards,
gg

>>> 


Thanks for the info.

I'll see if I have a chance to test the new UI.

I wonder if it makes sense, for the next time, to have tags with version
numbers instead of names that are difficult to track. Also, it may make
sense to create branches instead of tags, in order to be able to
backport bugfixes to them? Just my 2cents.

Thanks,

Andrés


GG Hegde wrote:
> All the changes are in trunk. For the pre change we have a tagged it as
> follows.
> https://forgesvn1.novell.com/viewsvn/simias/tags/preuichange/
> https://forgesvn1.novell.com/viewsvn/ifolder/tags/preuichange/
>  
> thanks and regards,
> gg
> 

> 
> Hey, this sound like great improvements.
> 
> In which version will they appear? Do we have a more stable 3.7 branch
> without them?
> 
> Thanks,
> 
> Andrés
> 
> 
> GG Hegde wrote:
>> iFolder has a new UI, the idea was to enhance the usability by brining
>> in certain change without changing the functionality of the current
> iFolder.
>> 1. Added toolbar and buttons for easy actions.
>> 2. Added the much needed information into the bottom panel.
>> 3. Added the panel which helps in connecting and disconnecting from the
>> domain.
>> 4. Refreshed some of the icons to bring in consistancy.
>> 5. Key recovery ( passphrase recovery) is made easier and now comes with
>> a UI.
>> 6. Brought in the consistency in the iFolder jargons used on the UI,
>> simplied to simple English like.
>> 7. Thumbnail view is changed to Details view with stress on information
>> and this view is selected by default.
>> 
>> These are few of the changes done. These changes were arrived at after
>> having the inputs from Human Factors team, iFolder users and iFolder
>> Administrators.
>> 
>> Request all to start using the new iFolder and give your feedback. There
>> are some minor issues, will sort it out in coming days.
>> 
>> thanks and regards,
>> GG
>>
>
>> I'll try to creata a new appliance today.
>>
>> Stephen
>>
>> On Jun 3, 2009, at 6:38 AM, "Balakrishnan KalIdas"
>>  wrote:
>>
>>> Hi All,
>>>
>>> There are multiple code check-ins and updates in the trunk. The new
>>> UI code is getting merged to the trunk as well. Support for 2.4 Mono
>>> is now available. Some spec file changes are required now which we
>>> are completing now. Multiple builds are being done to ensure we do
>>> not break anything.
>>>
>>> It would be great if some of you can do more builds and ensure that
>>> OpenSuSE 11.1 and other distributions are not broken.
>>>
>>> Wait for the updated spec file check-in that will happen in another
>>> few hours - post testing.
>>>
>>> GG Hegde will send an update soon about the new UI. He is
>>> spearheading that effort along with Human factors.
>>>
>>> Kalis
>>>
>>> ___
>>> ifolder-dev mailing list
>>> ifolder-dev@forge.novell.com
>>> http://forge.novell.com/mailman/listinfo/ifolder-dev
>> ___
>> ifolder-dev mailing list
>> ifolder-dev@forge.novell.com
>> http://forge.novell.com/mailman/listinfo/ifolder-dev
>>
>>
>> 
>>
>> ___
>> ifolder-dev mailing list
>> ifolder-dev@forge.novell.com
>> http://forge.novell.com/mailman/listinfo/ifolder-dev
> 
> ___
> ifolder-dev mailing list
> ifolder-dev@forge.novell.com
> http://forgenovell.com/mailman/listinfo/ifolder-dev
> 
> 
> 
> 
> 
> ___
> ifolder-dev mailing list
> ifolder-dev@forge.novell.com
> http://forge.novell.com/mailman/

Re: [Ifolder-dev] Re: Bugs

2009-06-15 Thread Balakrishnan KalIdas 
For existing bugs that are still reproducible in 3.7 code base, we will just a 
comment mentioning, that it is valid in 3.7, so that we can get it fixed.

Yes, we need to mark them RESOLVED, unless the entire claim of a bug is invalid 
or the product is not designed to handle the case.

Kalis

>>> Brent McConnell  06/15/09 6:55 PM >>>
In my case I was looking at Linux client bugs and testing them on the 
3.7.2 client.  If they had been resolved I marked them as RESOLVED.

In one case the bug still existed and I added a comment describing the 
outcome of my test.  This brings up a good question how should this 
particular bug be handled.  It was filed against 3.6 and apparently 
still exists.  Should it be left OPEN or assigned some other status?  
Should the version be changed to reflect the current release?


Brent


GG Hegde wrote:
> Resolved few as FIXED after testing it on the current code as current 
> code has the fix, marked for NEEDINFO for which we cant test and need 
> some help from originator. Did not mark anything as INVALID as it may 
> be valid on that particular release.
> thanks and regards,
> gg
> >>>
>
> Hey guys, I don't follow, are you fixing them or marking them as
> NEEDINFO or closing them as INVALID or..?
>
> Thanks,
>
> Andrés
>
>
>
> Brent McConnell wrote:.
> >
> >
> > I got 2.
> >
>  "GG Hegde" 
> > 6/12/2009 2:28 PM >>>
> >
> > Reduced by 7.
> >
> > gg
> >
> >
> > 
> >
> > ___
> > ifolder-dev mailing list
> > ifolder-dev@forge.novell.com
> > http://forge.novell.com/mailman/listinfo/ifolder-dev
>
> ___
> ifolder-dev mailing list
> ifolder-dev@forge.novell.com
> http://forge.novell.com/mailman/listinfo/ifolder-dev
>
> 
>
> ___
> ifolder-dev mailing list
> ifolder-dev@forge.novell.com
> http://forge.novell.com/mailman/listinfo/ifolder-dev

___
ifolder-dev mailing list
ifolder-dev@forge.novell.com
http://forge.novell.com/mailman/listinfo/ifolder-dev

Re: [Ifolder-dev] Re: Bugs

2009-06-15 Thread Brent McConnell 
In my case I was looking at Linux client bugs and testing them on the 
3.7.2 client.  If they had been resolved I marked them as RESOLVED.


In one case the bug still existed and I added a comment describing the 
outcome of my test.  This brings up a good question how should this 
particular bug be handled.  It was filed against 3.6 and apparently 
still exists.  Should it be left OPEN or assigned some other status?  
Should the version be changed to reflect the current release?



Brent


GG Hegde wrote:
Resolved few as FIXED after testing it on the current code as current 
code has the fix, marked for NEEDINFO for which we cant test and need 
some help from originator. Did not mark anything as INVALID as it may 
be valid on that particular release.

thanks and regards,
gg
>>>

Hey guys, I don't follow, are you fixing them or marking them as
NEEDINFO or closing them as INVALID or..?

Thanks,

Andrés



Brent McConnell wrote:.
>
>
> I got 2.
>
 "GG Hegde" 
> 6/12/2009 2:28 PM >>>
>
> Reduced by 7.
>
> gg
>
>
> 
>
> ___
> ifolder-dev mailing list
> ifolder-dev@forge.novell.com
> http://forge.novell.com/mailman/listinfo/ifolder-dev

___
ifolder-dev mailing list
ifolder-dev@forge.novell.com
http://forge.novell.com/mailman/listinfo/ifolder-dev



___
ifolder-dev mailing list
ifolder-dev@forge.novell.com
http://forge.novell.com/mailman/listinfo/ifolder-dev
___
ifolder-dev mailing list
ifolder-dev@forge.novell.com
http://forge.novell.com/mailman/listinfo/ifolder-dev

[Ifolder-dev] Re: Update

2009-06-15 Thread GG Hegde 
Sure we could follow the tagging with the version no. too.
For the newui there was branch created and was merged back to trunk only after 
the development. As this UI has undergone the usability and Human Factor 
guidelines, it would be good to continue with the new one. We shall fix all the 
minor glitches if we have any.
 
thanks and regards,
gg

>>> 


Thanks for the info.

I'll see if I have a chance to test the new UI.

I wonder if it makes sense, for the next time, to have tags with version
numbers instead of names that are difficult to track. Also, it may make
sense to create branches instead of tags, in order to be able to
backport bugfixes to them? Just my 2cents.

Thanks,

Andrés


GG Hegde wrote:
> All the changes are in trunk. For the pre change we have a tagged it as
> follows.
> https://forgesvn1.novell.com/viewsvn/simias/tags/preuichange/
> https://forgesvn1.novell.com/viewsvn/ifolder/tags/preuichange/
>  
> thanks and regards,
> gg
> 

> 
> Hey, this sound like great improvements.
> 
> In which version will they appear? Do we have a more stable 3.7 branch
> without them?
> 
> Thanks,
> 
> Andrés
> 
> 
> GG Hegde wrote:
>> iFolder has a new UI, the idea was to enhance the usability by brining
>> in certain change without changing the functionality of the current
> iFolder.
>> 1. Added toolbar and buttons for easy actions.
>> 2. Added the much needed information into the bottom panel.
>> 3. Added the panel which helps in connecting and disconnecting from the
>> domain.
>> 4. Refreshed some of the icons to bring in consistancy.
>> 5. Key recovery ( passphrase recovery) is made easier and now comes with
>> a UI.
>> 6. Brought in the consistency in the iFolder jargons used on the UI,
>> simplied to simple English like.
>> 7. Thumbnail view is changed to Details view with stress on information
>> and this view is selected by default.
>> 
>> These are few of the changes done. These changes were arrived at after
>> having the inputs from Human Factors team, iFolder users and iFolder
>> Administrators.
>> 
>> Request all to start using the new iFolder and give your feedback. There
>> are some minor issues, will sort it out in coming days.
>> 
>> thanks and regards,
>> GG
>>
>
>> I'll try to creata a new appliance today.
>>
>> Stephen
>>
>> On Jun 3, 2009, at 6:38 AM, "Balakrishnan KalIdas"
>>  wrote:
>>
>>> Hi All,
>>>
>>> There are multiple code check-ins and updates in the trunk. The new
>>> UI code is getting merged to the trunk as well. Support for 2.4 Mono
>>> is now available. Some spec file changes are required now which we
>>> are completing now. Multiple builds are being done to ensure we do
>>> not break anything.
>>>
>>> It would be great if some of you can do more builds and ensure that
>>> OpenSuSE 11.1 and other distributions are not broken.
>>>
>>> Wait for the updated spec file check-in that will happen in another
>>> few hours - post testing.
>>>
>>> GG Hegde will send an update soon about the new UI. He is
>>> spearheading that effort along with Human factors.
>>>
>>> Kalis
>>>
>>> ___
>>> ifolder-dev mailing list
>>> ifolder-dev@forge.novell.com
>>> http://forge.novell.com/mailman/listinfo/ifolder-dev
>> ___
>> ifolder-dev mailing list
>> ifolder-dev@forge.novell.com
>> http://forge.novell.com/mailman/listinfo/ifolder-dev
>>
>>
>> 
>>
>> ___
>> ifolder-dev mailing list
>> ifolder-dev@forge.novell.com
>> http://forge.novell.com/mailman/listinfo/ifolder-dev
> 
> ___
> ifolder-dev mailing list
> ifolder-dev@forge.novell.com
> http://forgenovell.com/mailman/listinfo/ifolder-dev
> 
> 
> 
> 
> 
> ___
> ifolder-dev mailing list
> ifolder-dev@forge.novell.com
> http://forge.novell.com/mailman/listinfo/ifolder-dev

___
ifolder-dev mailing list
ifolder-dev@forge.novell.com
http://forge.novell.com/mailman/listinfo/ifolder-dev
___
ifolder-dev mailing list
ifolder-dev@forge.novell.com
http://forge.novell.com/mailman/listinfo/ifolder-dev

[Ifolder-dev] Re: Bugs

2009-06-15 Thread GG Hegde 
Resolved few as FIXED after testing it on the current code as current code has 
the fix, marked for NEEDINFO for which we cant test and need some help from 
originator. Did not mark anything as INVALID as it may be valid on that 
particular release.
 
thanks and regards,
gg
>>> 


Hey guys, I don't follow, are you fixing them or marking them as
NEEDINFO or closing them as INVALID or..?

Thanks,

Andrés



Brent McConnell wrote:.
> 
> 
> I got 2.
> 
 "GG Hegde" 
> 6/12/2009 2:28 PM >>>
> 
> Reduced by 7.
> 
> gg
> 
> 
> 
> 
> ___
> ifolder-dev mailing list
> ifolder-dev@forge.novell.com
> http://forge.novell.com/mailman/listinfo/ifolder-dev

___
ifolder-dev mailing list
ifolder-dev@forge.novell.com
http://forge.novell.com/mailman/listinfo/ifolder-dev
___
ifolder-dev mailing list
ifolder-dev@forge.novell.com
http://forge.novell.com/mailman/listinfo/ifolder-dev