yellow team mailing list archive

[Gary Poster <gary.poster@xxxxxxxxxxxxx>]

Hi Danilo.  Thank you for these summaries!

It sounds like you would estimate this to be at least a week's work for you, and more for someone not familiar with the code?  Or maybe two weeks for you?

While I'm asking for estimates, it sounds like bug 734765 wouldn't exactly be trivial itself.  Three or four days for you, more for others?

Does this bug fix need to be coordinated with the other one in any way, or are they sufficiently separate so as to not be a worry?

Gary


On Jun 23, 2011, at 6:39 AM, Danilo Šegan wrote:

> Hi all,
> 
> Bug 775691 is much harder than the other one, because it is a bug
> introduced in the very sensitive code for the entire translation app:
> setCurrentTranslation.
> 
> FWIW, this basically breaks entire sharing concept for translations and
> I can't believe it was introduced.  Also, the fact that this sharing
> doesn't really happen anymore might indicate why bug 603530 was suddenly
> fixed on March 1st (if we don't try to do complex stuff, we are not
> going to go wrong with it anyway).  That's just a guess, but I suspect
> landing from around that period broke sharing in significant ways.
> 
> Now, the problem is that the only two people really intimately familiar
> with this code are Jeroen and me.  But, I am willing to walk anyone
> through our mental process and implementation of the method.  Critical
> to understanding it is the design spec at:
> 
> 
> https://dev.launchpad.net/Translations/Specs/UpstreamImportIntoUbuntu/FixingIsImported/setCurrentTranslation
> 
> I believe this is very urgent for fixing for translations.  And I am
> very sad that this has gone through.
> 
> Cheers,
> Danilo
> 
> 
> 
> -- 
> Mailing list: https://launchpad.net/~yellow
> Post to     : yellow@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yellow
> More help   : https://help.launchpad.net/ListHelp