Thanks Matthew. Great suggestions. Yes, we did add the check to
parsekey and I just ran everything through the check and fixed the
remaining errors.
for i in `grep "^Name=" /usr/share/sword/locales.d/*.conf|cut -f2
-d=|sort|uniq`; do ./parsekey jn.1.1 $i; done
I'm building with ICU so I on
On Mon, Apr 27, 2009 at 12:50 PM, Troy A. Griffitts wrote:
> Jonathan Marsden wrote:
>
>> Troy A. Griffitts wrote:
>> Good :)
>>
>> Is there is list of all known release-critical bugs and TODO items
>> somewhere?
>>
>
> No, the bugtracker is clean now for critical 1.6.x changes, as far as I
> know
> Data changes (as in .conf files and so forth), sure (it would be nice if
> there was a .conf file validator though). Touch a .h or .cpp file and
> you're probably looking at another RC, to be safe :)
I'm not sure I understand the locales .conf files at this point well
enough to help out with va
2009/4/27 Jonathan Marsden :
> Troy A. Griffitts wrote:
>
>> so if we only get those changes over the next couple days, let's
>> shoot to release a final on Tuesday evening PST. ...
>
>> How's that for a plan?
>
> Well, I'd suggest a bit more time between RC3 and final, say a week --
> so we can ge
Troy A. Griffitts wrote:
>> is it perhaps time for an RC3 and a freeze on all non-essential
>> changes until we can get a final 1.6 "out the door"??
> Yeah, I'd say so. I'm about to head out to evening service at Church
> since I slept in this morning :)
If I did that, someone would probably co
Jonathan Marsden wrote:
Troy A. Griffitts wrote:
Good :)
Is there is list of all known release-critical bugs and TODO items
somewhere?
No, the bugtracker is clean now for critical 1.6.x changes, as far as I
know (right?). We're only fixing feedback we get on the RCs now.
The only outstandi
