On Tue, May 23, 2006 at 09:00:39PM -0300, bulia byak wrote:
On 5/23/06, Bryce Harrington <bryce@...961...> wrote:
I think these feature changes all are great to see (although I'll be sad to see the default fill-opacity go away), but since we're in a freeze from new features, and are going into feature freeze, I think it would be wise to propose these changes before committing them. I'm sure all of these would get the thumbs up, but just in case you have some additional last minute changes up your sleeves. ;-)
Sorry, I didn't think it applied to this - it's not coding changes, just changes in settings. Almost the same as e.g. adding a new palette or translation.
By themselves they cannot introduce new bugs (though they can expose some existing bugs, which is what happened today - I fixed a crash).
Okay, sounds safe enough, although reminds me of an old story with some punchline about, "But the only change I made was to a comment!!" ;-)
But you're right, it may be worthwhile to distinguish these sorts of non-code changes from code ones. Still, it might be safest to count them as features for purposes of freezing - as you pointed out, they could expose other kinds of bugs. Additionally, these files sometimes contain translatable text, so freezing them may benefit translators in making it easier for them to hit their translation targets.
Bryce