You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Tony Wu <wu...@gmail.com> on 2007/04/18 07:45:17 UTC
[classlib]complete java 6 api(Agreement and call for volunteers)
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.
2. Make your patch as small as possible so that it won't take much
time to understand.
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?
[1]
http://harmony.apache.org/issue_resolution_guideline.html
[2]
http://wiki.apache.org/harmony/ClasslibJava6
--
Tony Wu
China Software Development Lab, IBM
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by LvJimmy，Jing <fi...@gmail.com>.
2007/4/18, Alexey Petrenko <al...@gmail.com>:
> 2007/4/18, Tony Wu <wu...@gmail.com>:
> > 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.
> It looks like we do not have "[component][module]" requirement in
> Harmony guidelines at all. But it would be nice to have :)
>
> > 2. Make your patch as small as possible so that it won't take much
> > time to understand.
> This can be applied to ALL the patches and it also would be nice if
> ALL the patches will have patch descriptions :)
>
> > 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?
> We still got ~3% of unimplemented API in AWT/Swing area for Java5. Not
> very important API but... :)
> So we will need to synchronize our AWT/Swing development with Java6 branch.
>
> BTW here is japitool comparison between Java6 and Harmony [1]. We have
> 89.25% success rate. The main development areas (new packages) are
> org.xml, javax.ws, javax.util, javax.script, javax.lang,
> javax.activation, javax.annotation.
>
> So there are a lot of places to work on :)
>
Yes, I think so, we may still focus on java5 API coverage, bug-fixing
and tools. And for those who interests in further development for
Harmony, they can take a pioneer step :)
> SY, Alexey
>
--
Best Regards!
Jimmy, Jing Lv
China Software Development Lab, IBM
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Sean Qiu <se...@gmail.com>.
Thanks, Tony
And i'd like to focus on the archive module.
2007/4/18, Tony Wu <wu...@gmail.com>:
> Thanks Alexey, I think the comparison[1] between java6 and java5 is also useful.
> [1]
> http://www.kaffe.org/~stuart/japi/htmlout/h-jdk6-jdk15.html
>
> On 4/18/07, Alexey Petrenko <al...@gmail.com> wrote:
> > oops, here is a link to japitool comparison:
> > http://www.kaffe.org/~stuart/japi/htmlout/h-jdk6-harmony.html :)
> >
> > 2007/4/18, Alexey Petrenko <al...@gmail.com>:
> > > 2007/4/18, Tony Wu <wu...@gmail.com>:
> > > > 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.
> > > It looks like we do not have "[component][module]" requirement in
> > > Harmony guidelines at all. But it would be nice to have :)
> > >
> > > > 2. Make your patch as small as possible so that it won't take much
> > > > time to understand.
> > > This can be applied to ALL the patches and it also would be nice if
> > > ALL the patches will have patch descriptions :)
> > >
> > > > 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?
> > > We still got ~3% of unimplemented API in AWT/Swing area for Java5. Not
> > > very important API but... :)
> > > So we will need to synchronize our AWT/Swing development with Java6 branch.
> > >
> > > BTW here is japitool comparison between Java6 and Harmony [1]. We have
> > > 89.25% success rate. The main development areas (new packages) are
> > > org.xml, javax.ws, javax.util, javax.script, javax.lang,
> > > javax.activation, javax.annotation.
> > >
> > > So there are a lot of places to work on :)
> > >
> > > SY, Alexey
> > >
> >
>
>
> --
> Tony Wu
> China Software Development Lab, IBM
>
--
Sean Qiu
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Tony Wu <wu...@gmail.com>.
Thanks Alexey, I think the comparison[1] between java6 and java5 is also useful.
[1]
http://www.kaffe.org/~stuart/japi/htmlout/h-jdk6-jdk15.html
On 4/18/07, Alexey Petrenko <al...@gmail.com> wrote:
> oops, here is a link to japitool comparison:
> http://www.kaffe.org/~stuart/japi/htmlout/h-jdk6-harmony.html :)
>
> 2007/4/18, Alexey Petrenko <al...@gmail.com>:
> > 2007/4/18, Tony Wu <wu...@gmail.com>:
> > > 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.
> > It looks like we do not have "[component][module]" requirement in
> > Harmony guidelines at all. But it would be nice to have :)
> >
> > > 2. Make your patch as small as possible so that it won't take much
> > > time to understand.
> > This can be applied to ALL the patches and it also would be nice if
> > ALL the patches will have patch descriptions :)
> >
> > > 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?
> > We still got ~3% of unimplemented API in AWT/Swing area for Java5. Not
> > very important API but... :)
> > So we will need to synchronize our AWT/Swing development with Java6 branch.
> >
> > BTW here is japitool comparison between Java6 and Harmony [1]. We have
> > 89.25% success rate. The main development areas (new packages) are
> > org.xml, javax.ws, javax.util, javax.script, javax.lang,
> > javax.activation, javax.annotation.
> >
> > So there are a lot of places to work on :)
> >
> > SY, Alexey
> >
>
--
Tony Wu
China Software Development Lab, IBM
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Alexey Petrenko <al...@gmail.com>.
oops, here is a link to japitool comparison:
http://www.kaffe.org/~stuart/japi/htmlout/h-jdk6-harmony.html :)
2007/4/18, Alexey Petrenko <al...@gmail.com>:
> 2007/4/18, Tony Wu <wu...@gmail.com>:
> > 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.
> It looks like we do not have "[component][module]" requirement in
> Harmony guidelines at all. But it would be nice to have :)
>
> > 2. Make your patch as small as possible so that it won't take much
> > time to understand.
> This can be applied to ALL the patches and it also would be nice if
> ALL the patches will have patch descriptions :)
>
> > 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?
> We still got ~3% of unimplemented API in AWT/Swing area for Java5. Not
> very important API but... :)
> So we will need to synchronize our AWT/Swing development with Java6 branch.
>
> BTW here is japitool comparison between Java6 and Harmony [1]. We have
> 89.25% success rate. The main development areas (new packages) are
> org.xml, javax.ws, javax.util, javax.script, javax.lang,
> javax.activation, javax.annotation.
>
> So there are a lot of places to work on :)
>
> SY, Alexey
>
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Alexey Petrenko <al...@gmail.com>.
2007/4/18, Tony Wu <wu...@gmail.com>:
> 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.
It looks like we do not have "[component][module]" requirement in
Harmony guidelines at all. But it would be nice to have :)
> 2. Make your patch as small as possible so that it won't take much
> time to understand.
This can be applied to ALL the patches and it also would be nice if
ALL the patches will have patch descriptions :)
> 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?
We still got ~3% of unimplemented API in AWT/Swing area for Java5. Not
very important API but... :)
So we will need to synchronize our AWT/Swing development with Java6 branch.
BTW here is japitool comparison between Java6 and Harmony [1]. We have
89.25% success rate. The main development areas (new packages) are
org.xml, javax.ws, javax.util, javax.script, javax.lang,
javax.activation, javax.annotation.
So there are a lot of places to work on :)
SY, Alexey
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Yang Paulex <pa...@gmail.com>.
2007/4/23, Stepan Mishura <st...@gmail.com>:
>
> On 4/23/07, Yang Paulex wrote:
> > 2007/4/19, LvJimmy，Jing :
> > >
> > > Sounds great :)
> > >
> > > 2007/4/18, Tony Wu <wu...@gmail.com>:
> > > > 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?
> >
>
> I think we should make it editable.
Great, then, who knows how? :)
Thanks,
> Stepan.
>
> > > 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
> >
>
>
> --
> Stepan Mishura
> Intel Enterprise Solutions Software Division
>
--
Paulex Yang
China Software Development laboratory
IBM
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Stepan Mishura <st...@gmail.com>.
On 4/23/07, Yang Paulex wrote:
> 2007/4/19, LvJimmy，Jing :
> >
> > Sounds great :)
> >
> > 2007/4/18, Tony Wu <wu...@gmail.com>:
> > > 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?
>
I think we should make it editable.
Thanks,
Stepan.
> > 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
>
--
Stepan Mishura
Intel Enterprise Solutions Software Division
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Tony Wu <wu...@gmail.com>.
Thanks, that's great!
On 4/23/07, Rui Hu <ro...@gmail.com> wrote:
> I'm interesting at the top 3 components in
> http://www.kaffe.org/~stuart/japi/htmlout/h-jdk6-harmony.html
> So, I'll be the volunteer to finish the update of :
> java.lang
> java.lang.annotation
> java.lang.instrument
>
> Thanks.
>
> On 4/23/07, Tony Wu <wu...@gmail.com> wrote:
> >
> > It's great if we can get support from JIRA system. Before that, I
> > would like to take jimmy's advice temporarily since it is compatible
> > with existing pattern. IIRC someone has writtern a tool to parse the
> > JIRA according to this pattern.
> >
> > On 4/23/07, Yang Paulex <pa...@gmail.com> wrote:
> > > 2007/4/19, LvJimmy，Jing <fi...@gmail.com>:
> > > >
> > > > Sounds great :)
> > > >
> > > > 2007/4/18, Tony Wu <wu...@gmail.com>:
> > > > > 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?
> > >
> > > > 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
> > >
> >
> >
> > --
> > Tony Wu
> > China Software Development Lab, IBM
> >
>
>
>
> --
> Robert Hu
> China Software Development Lab, IBM
>
--
Tony Wu
China Software Development Lab, IBM
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Rui Hu <ro...@gmail.com>.
I'm interesting at the top 3 components in
http://www.kaffe.org/~stuart/japi/htmlout/h-jdk6-harmony.html
So, I'll be the volunteer to finish the update of :
java.lang
java.lang.annotation
java.lang.instrument
Thanks.
On 4/23/07, Tony Wu <wu...@gmail.com> wrote:
>
> It's great if we can get support from JIRA system. Before that, I
> would like to take jimmy's advice temporarily since it is compatible
> with existing pattern. IIRC someone has writtern a tool to parse the
> JIRA according to this pattern.
>
> On 4/23/07, Yang Paulex <pa...@gmail.com> wrote:
> > 2007/4/19, LvJimmy，Jing <fi...@gmail.com>:
> > >
> > > Sounds great :)
> > >
> > > 2007/4/18, Tony Wu <wu...@gmail.com>:
> > > > 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?
> >
> > > 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
> >
>
>
> --
> Tony Wu
> China Software Development Lab, IBM
>
--
Robert Hu
China Software Development Lab, IBM
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Tony Wu <wu...@gmail.com>.
It's great if we can get support from JIRA system. Before that, I
would like to take jimmy's advice temporarily since it is compatible
with existing pattern. IIRC someone has writtern a tool to parse the
JIRA according to this pattern.
On 4/23/07, Yang Paulex <pa...@gmail.com> wrote:
> 2007/4/19, LvJimmy，Jing <fi...@gmail.com>:
> >
> > Sounds great :)
> >
> > 2007/4/18, Tony Wu <wu...@gmail.com>:
> > > 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?
>
> > 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
>
--
Tony Wu
China Software Development Lab, IBM
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Andrew Zhang <zh...@gmail.com>.
On 4/23/07, Yang Paulex <pa...@gmail.com> wrote:
>
> 2007/4/19, LvJimmy，Jing <fi...@gmail.com>:
> >
> > Sounds great :)
> >
> > 2007/4/18, Tony Wu <wu...@gmail.com>:
> > > 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
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Yang Paulex <pa...@gmail.com>.
2007/4/19, LvJimmy，Jing <fi...@gmail.com>:
>
> Sounds great :)
>
> 2007/4/18, Tony Wu <wu...@gmail.com>:
> > 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?
> 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
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by LvJimmy，Jing <fi...@gmail.com>.
Sounds great :)
2007/4/18, Tony Wu <wu...@gmail.com>:
> 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 :)
> 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
Re: [classlib]complete java 6 api(Agreement and call for volunteers)
Posted by Alexey Varlamov <al...@gmail.com>.
It would be nice to add some info on changes between v5 and v6, maybe
a reference to JAPI report or smth.
2007/4/18, Tony Wu <wu...@gmail.com>:
> 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.
>
> 2. Make your patch as small as possible so that it won't take much
> time to understand.
>
>
>
> 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?
>
> [1]
> http://harmony.apache.org/issue_resolution_guideline.html
> [2]
> http://wiki.apache.org/harmony/ClasslibJava6
>
>
> --
> Tony Wu
> China Software Development Lab, IBM
>