On 4/23/07, Yang Paulex <[EMAIL PROTECTED]> wrote:
2007/4/19, LvJimmy，Jing <[EMAIL PROTECTED]>: > > Sounds great :) > > 2007/4/18, Tony Wu <[EMAIL PROTECTED]>: > > Thanks Stepan and all the people who helped to boost, now we have a > > branch for java 6 classlib. > > > > Before we start to complete the new feature, I think we should have an > > agreement addition to Good issue resolution guideline[1]. > > > > I just draft 2 points here in order to use the little to get the big. > > > > 1. The suggested pattern of JIRA Summary is > > [java6][classlib][$module]blabla.. so that it is easy for committers > > to know where the patch should be applied. > > > > Maybe [classlib][$module][Harmony6] is better? Personal suggestion :) I suppose JIRA can be used to tracking versions for this purpose? But seems the "affected version" cannot be changed when raising new JIRAs. Any suggestions from JIRA gurus?
Yes Paulex. I'm not a JIRA guru, but I know JIRA supports for this purpose. :) Developers can select multiple versions in affected version(s) and fixed version(s) when filing and closing a JIRA issue.
2. Make your patch as small as possible so that it won't take much > > time to understand. > > > > Yes, committers will be busy :) > > > > > > > I'll start with io and nio_char module. I have created a page on > > harmony wiki [2] to record the work. any volunteer on other modules? > > > > I'm interested in nio and java.net :) > > > [1] > > http://harmony.apache.org/issue_resolution_guideline.html > > [2] > > http://wiki.apache.org/harmony/ClasslibJava6 > > > > > > -- > > Tony Wu > > China Software Development Lab, IBM > > > > > -- > > Best Regards! > > Jimmy, Jing Lv > China Software Development Lab, IBM > -- Paulex Yang China Software Development laboratory IBM
-- Best regards, Andrew Zhang
