Hi, Vlad,
such a policy is not documented anywhere, but we've already had a
precedent. See the attached email from Mark.
Thanks,
Artem
On 5/24/2013 1:29 PM, Vladislav Karnaukhov wrote:
Hello Anthony,
do we have a policy with requires us to provide bug description in
lowercase-only? I can see that may other bugs were reviewed and pushed
without their titles edited...
I'm not aware of such a policy; could you please point at it?
Regards,
- Vlad
On 5/24/2013 01:23 PM, Anthony Petrov wrote:
Dmitry,
Please fix the case of the letters in the synopsis for this bug in JBS,
and also please remember to use the fixed title in your hg commit
message. You shouldn't push a changeset with all-caps title in the
repository. Thanks.
--
best regards,
Anthony
On 05/24/2013 11:46 AM, dmitry markov wrote:
Hello,
Could toy review the fix:
bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=8014863
webrev: http://cr.openjdk.java.net/~vkarnauk/8014863/webrev.00/
The fix removes break points caching from GlyphView. If some text is
inserted/removed into/from the document contained several elements, all
elements views will re-calculate their break points.
Thanks,
Dmitry.
--- Begin Message ---
2013/4/28 23:56 -0700, [email protected]:
> Changeset: 2b8bd577257c
> Author: mcherkas
> Date: 2013-04-29 17:54 +0400
> URL: http://hg.openjdk.java.net/jdk8/awt/jdk/rev/2b8bd577257c
>
> 8012004: JINTERNALFRAME NOT BEING FINALIZED AFTER CLOSING
Please capitalize bug synopses correctly. Just because one of Oracle's
internal systems forces bug synopses to be upper-case is no reason to
litter the OpenJDK change history with such ugliness.
I've backed out this changeset and blacklisted it. Please create a new
changeset with a properly-capitalized synopsis.
- Mark
--- End Message ---
