You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Tim Ellison <t....@gmail.com> on 2009/04/17 13:23:42 UTC
[general] Lesson and roadmap thoughts
Immediately after a release is usually the time that I'm thinking about
lessons learned, the project road map, and future deliveries from Harmony.
Most noticeable for me was the long stabilization period we undertook
for M9 compared to earlier releases. This was required, I believe,
because of the longer open development period [1]. The lesson to take
away from that is to ensure we keep an eye on our regular release
schedule and keep the time boxes short enough that stable fixes get out
to our users, and we minimize the frozen codebase period.
Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
May (6 weeks after April 8th = May 20).
The other thing that bothers me is the lack of expose we give our Java 6
branch. While the majority of fixes we commit are applied to both
branches, we have some good work completed in the Java 6 API branch's
core classes that is not getting the uptake it deserves.
The non-core Java 6 classes get very little attention at the moment.
With Harmony's strong modular architecture we can easily construct a
headless runtime that delivers those core classes without the missing
functionality.
I'd like to suggest that we experiment with the flexible components in
Harmony to deliver a headless runtime based on the Java 6 APIs.
Thoughts?
[1] Depending on exactly how you count it, we were open from 17 Nov - 27
Feb, which is a massive 14.5 weeks!
Regards,
Tim
Re: [general] Lesson and roadmap thoughts
Posted by Dan Bornstein <da...@google.com>.
2009/4/21 Alexei Fedotov <al...@gmail.com>:
> Well, at least it would be nice to know that subsequent Java 5
> releases are of some interest for somebody. Otherwise, why should we
> spend time for creating and testing two releases instead of the latest
> one?
FWIW, the Dalvik (Android) project has no plans to switch off of the 5
codebase any time soon. I know we aren't customers[*] of the entire
project, but I figure I'd add the data point.
-dan
[*] I don't mind that term.
Re: [general] Lesson and roadmap thoughts
Posted by Alexei Fedotov <al...@gmail.com>.
Tim, thanks for explanation. It seems there are people around. :-)
2009/4/22 Tim Ellison <t....@gmail.com>:
> Alexei Fedotov wrote:
>> Hello,
>>
>>> and I don't think
>>> anyone is suggesting that we stop Java 5 'cold' and switch to Java 6
>>> branch releases.
>>
>> Well, at least it would be nice to know that subsequent Java 5
>> releases are of some interest for somebody. Otherwise, why should we
>> spend time for creating and testing two releases instead of the latest
>> one?
>
> How do we know that the current Java 5 releases are of interest to
> people :-) ?
>
> Seriously though, as long as there are people around here who are
> prepared to contribute to the upkeep of the Java 5 stream, and its
> milestone releases, then I don't see why we would summarily terminate them.
>
> Regards,
> Tim
>
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://www.telecom-express.ru/
http://people.apache.org/~aaf/
http://harmony.apache.org/
http://code.google.com/p/openmeetings/
Re: [general] Lesson and roadmap thoughts
Posted by Tim Ellison <t....@gmail.com>.
Alexei Fedotov wrote:
> Hello,
>
>> and I don't think
>> anyone is suggesting that we stop Java 5 'cold' and switch to Java 6
>> branch releases.
>
> Well, at least it would be nice to know that subsequent Java 5
> releases are of some interest for somebody. Otherwise, why should we
> spend time for creating and testing two releases instead of the latest
> one?
How do we know that the current Java 5 releases are of interest to
people :-) ?
Seriously though, as long as there are people around here who are
prepared to contribute to the upkeep of the Java 5 stream, and its
milestone releases, then I don't see why we would summarily terminate them.
Regards,
Tim
Re: [general] Lesson and roadmap thoughts
Posted by Alexei Fedotov <al...@gmail.com>.
Hello,
> and I don't think
> anyone is suggesting that we stop Java 5 'cold' and switch to Java 6
> branch releases.
Well, at least it would be nice to know that subsequent Java 5
releases are of some interest for somebody. Otherwise, why should we
spend time for creating and testing two releases instead of the latest
one?
On Tue, Apr 21, 2009 at 11:01 PM, Tim Ellison <t....@gmail.com> wrote:
> Nathan Beyer wrote:
>> Maybe it is just me, but I really don't like calling our users
>> "customers". It makes me cringe when I hear that.
>
> How about "stakeholders" :-)
>
>> I don't think this question is sufficent. We need to consider JDK and
>> JRE uses separately. Yes, most java 5 code should run on a java 6 JRE,
>> but you wouldn't use a java 6 JDK for java 5 dev - it is too much of a
>> risk when compiling against the class library. I've seen this issue bite
>> back too many times.
>
> We can reassess once we have got the two on offer. For now we are only
> testing and releasing the Java 5 branch regularly, and I don't think
> anyone is suggesting that we stop Java 5 'cold' and switch to Java 6
> branch releases. There would have to be a reasonable overlap of (IMHO)
> two or three releases of both branches.
>
> Regards,
> Tim
>
>> On Apr 21, 2009, at 11:43 AM, Alexei Fedotov <al...@gmail.com>
>> wrote:
>>
>>> Alexey, thanks for interesting polls. Well, I believe we should state
>>> the question differently:
>>>
>>> How many java programs which run with Java 1.5 cannot be run using
>>> Java 1.6?
>>> Or even better: does Harmony have customers (including internal
>>> customers) which cannot easily switch to Java 6?
>>>
>>>
>>>
>>>
>>> 2009/4/21 Alexey Varlamov <al...@gmail.com>:
>>>> 20 апреля 2009 г. 15:47 пользователь Tim Ellison
>>>> <t....@gmail.com> написал:
>>>>> Alexei Fedotov wrote:
>>>>>> Under resource constraints we may even think of dropping Java 5 in
>>>>>> favor of
>>>>>> Java 6. This would save Java 6 supporters their merge efforts and
>>>>>> nullify
>>>>>> merge bugs.
>>>>>
>>>>> Maybe. I hadn't thought of going that far - at least, not without a
>>>>> reasonable overlap period that allows people to migrate from 5.0 to 6.0
>>>>> stream.
>>>>>
>>>>> Given we don't make a big deal of publishing the 6.0 stream code today,
>>>>> I think it would be unreasonable to abandon the 5.0 stream
>>>>> abruptly. We
>>>>> may well get to that point over time.
>>>>
>>>> In fact Java5 is still widely used (more than 1/3 of polled audience
>>>> on average), so surely we should not abandon it now.
>>>>
>>>> [1] http://www.misterpoll.com/polls/347384/results
>>>> [2]
>>>> http://www.jroller.com/scolebourne/entry/devoxx_2008_whiteboard_votes
>>>> [3] http://www.jivesoftware.com/jivespace/poll.jspa?poll=1021
>>>>
>>>> --
>>>> Alexey
>>>>
>>>
>>>
>>>
>>> --
>>> With best regards / с наилучшими пожеланиями,
>>> Alexei Fedotov / Алексей Федотов,
>>> http://www.telecom-express.ru/
>>> http://people.apache.org/~aaf/
>>> http://harmony.apache.org/
>>> http://code.google.com/p/openmeetings/
>>
>
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://www.telecom-express.ru/
http://people.apache.org/~aaf/
http://harmony.apache.org/
http://code.google.com/p/openmeetings/
Re: [general] Lesson and roadmap thoughts
Posted by Tim Ellison <t....@gmail.com>.
Nathan Beyer wrote:
> Maybe it is just me, but I really don't like calling our users
> "customers". It makes me cringe when I hear that.
How about "stakeholders" :-)
> I don't think this question is sufficent. We need to consider JDK and
> JRE uses separately. Yes, most java 5 code should run on a java 6 JRE,
> but you wouldn't use a java 6 JDK for java 5 dev - it is too much of a
> risk when compiling against the class library. I've seen this issue bite
> back too many times.
We can reassess once we have got the two on offer. For now we are only
testing and releasing the Java 5 branch regularly, and I don't think
anyone is suggesting that we stop Java 5 'cold' and switch to Java 6
branch releases. There would have to be a reasonable overlap of (IMHO)
two or three releases of both branches.
Regards,
Tim
> On Apr 21, 2009, at 11:43 AM, Alexei Fedotov <al...@gmail.com>
> wrote:
>
>> Alexey, thanks for interesting polls. Well, I believe we should state
>> the question differently:
>>
>> How many java programs which run with Java 1.5 cannot be run using
>> Java 1.6?
>> Or even better: does Harmony have customers (including internal
>> customers) which cannot easily switch to Java 6?
>>
>>
>>
>>
>> 2009/4/21 Alexey Varlamov <al...@gmail.com>:
>>> 20 апреля 2009 г. 15:47 пользователь Tim Ellison
>>> <t....@gmail.com> написал:
>>>> Alexei Fedotov wrote:
>>>>> Under resource constraints we may even think of dropping Java 5 in
>>>>> favor of
>>>>> Java 6. This would save Java 6 supporters their merge efforts and
>>>>> nullify
>>>>> merge bugs.
>>>>
>>>> Maybe. I hadn't thought of going that far - at least, not without a
>>>> reasonable overlap period that allows people to migrate from 5.0 to 6.0
>>>> stream.
>>>>
>>>> Given we don't make a big deal of publishing the 6.0 stream code today,
>>>> I think it would be unreasonable to abandon the 5.0 stream
>>>> abruptly. We
>>>> may well get to that point over time.
>>>
>>> In fact Java5 is still widely used (more than 1/3 of polled audience
>>> on average), so surely we should not abandon it now.
>>>
>>> [1] http://www.misterpoll.com/polls/347384/results
>>> [2]
>>> http://www.jroller.com/scolebourne/entry/devoxx_2008_whiteboard_votes
>>> [3] http://www.jivesoftware.com/jivespace/poll.jspa?poll=1021
>>>
>>> --
>>> Alexey
>>>
>>
>>
>>
>> --
>> With best regards / с наилучшими пожеланиями,
>> Alexei Fedotov / Алексей Федотов,
>> http://www.telecom-express.ru/
>> http://people.apache.org/~aaf/
>> http://harmony.apache.org/
>> http://code.google.com/p/openmeetings/
>
Re: [general] Lesson and roadmap thoughts
Posted by Nathan Beyer <nb...@gmail.com>.
Maybe it is just me, but I really don't like calling our users
"customers". It makes me cringe when I hear that.
I don't think this question is sufficent. We need to consider JDK and
JRE uses separately. Yes, most java 5 code should run on a java 6 JRE,
but you wouldn't use a java 6 JDK for java 5 dev - it is too much of a
risk when compiling against the class library. I've seen this issue
bite back too many times.
-nathan
Sent from my iPhone
On Apr 21, 2009, at 11:43 AM, Alexei Fedotov
<al...@gmail.com> wrote:
> Alexey, thanks for interesting polls. Well, I believe we should state
> the question differently:
>
> How many java programs which run with Java 1.5 cannot be run using
> Java 1.6?
> Or even better: does Harmony have customers (including internal
> customers) which cannot easily switch to Java 6?
>
>
>
>
> 2009/4/21 Alexey Varlamov <al...@gmail.com>:
>> 20 апреля 2009 г. 15:47 пользователь Tim Ellison
>> <t....@gmail.com> написал:
>>> Alexei Fedotov wrote:
>>>> Under resource constraints we may even think of dropping Java 5
>>>> in favor of
>>>> Java 6. This would save Java 6 supporters their merge efforts and
>>>> nullify
>>>> merge bugs.
>>>
>>> Maybe. I hadn't thought of going that far - at least, not without a
>>> reasonable overlap period that allows people to migrate from 5.0
>>> to 6.0
>>> stream.
>>>
>>> Given we don't make a big deal of publishing the 6.0 stream code
>>> today,
>>> I think it would be unreasonable to abandon the 5.0 stream
>>> abruptly. We
>>> may well get to that point over time.
>>
>> In fact Java5 is still widely used (more than 1/3 of polled audience
>> on average), so surely we should not abandon it now.
>>
>> [1] http://www.misterpoll.com/polls/347384/results
>> [2] http://www.jroller.com/scolebourne/entry/devoxx_2008_whiteboard_votes
>> [3] http://www.jivesoftware.com/jivespace/poll.jspa?poll=1021
>>
>> --
>> Alexey
>>
>
>
>
> --
> With best regards / с наилучшими пожеланиями,
> Alexei Fedotov / Алексей Федотов,
> http://www.telecom-express.ru/
> http://people.apache.org/~aaf/
> http://harmony.apache.org/
> http://code.google.com/p/openmeetings/
Re: [general] Lesson and roadmap thoughts
Posted by Alexei Fedotov <al...@gmail.com>.
Alexey, thanks for interesting polls. Well, I believe we should state
the question differently:
How many java programs which run with Java 1.5 cannot be run using Java 1.6?
Or even better: does Harmony have customers (including internal
customers) which cannot easily switch to Java 6?
2009/4/21 Alexey Varlamov <al...@gmail.com>:
> 20 апреля 2009 г. 15:47 пользователь Tim Ellison
> <t....@gmail.com> написал:
>> Alexei Fedotov wrote:
>>> Under resource constraints we may even think of dropping Java 5 in favor of
>>> Java 6. This would save Java 6 supporters their merge efforts and nullify
>>> merge bugs.
>>
>> Maybe. I hadn't thought of going that far - at least, not without a
>> reasonable overlap period that allows people to migrate from 5.0 to 6.0
>> stream.
>>
>> Given we don't make a big deal of publishing the 6.0 stream code today,
>> I think it would be unreasonable to abandon the 5.0 stream abruptly. We
>> may well get to that point over time.
>
> In fact Java5 is still widely used (more than 1/3 of polled audience
> on average), so surely we should not abandon it now.
>
> [1] http://www.misterpoll.com/polls/347384/results
> [2] http://www.jroller.com/scolebourne/entry/devoxx_2008_whiteboard_votes
> [3] http://www.jivesoftware.com/jivespace/poll.jspa?poll=1021
>
> --
> Alexey
>
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://www.telecom-express.ru/
http://people.apache.org/~aaf/
http://harmony.apache.org/
http://code.google.com/p/openmeetings/
Re: [general] Lesson and roadmap thoughts
Posted by Alexey Varlamov <al...@gmail.com>.
20 апреля 2009 г. 15:47 пользователь Tim Ellison
<t....@gmail.com> написал:
> Alexei Fedotov wrote:
>> Under resource constraints we may even think of dropping Java 5 in favor of
>> Java 6. This would save Java 6 supporters their merge efforts and nullify
>> merge bugs.
>
> Maybe. I hadn't thought of going that far - at least, not without a
> reasonable overlap period that allows people to migrate from 5.0 to 6.0
> stream.
>
> Given we don't make a big deal of publishing the 6.0 stream code today,
> I think it would be unreasonable to abandon the 5.0 stream abruptly. We
> may well get to that point over time.
In fact Java5 is still widely used (more than 1/3 of polled audience
on average), so surely we should not abandon it now.
[1] http://www.misterpoll.com/polls/347384/results
[2] http://www.jroller.com/scolebourne/entry/devoxx_2008_whiteboard_votes
[3] http://www.jivesoftware.com/jivespace/poll.jspa?poll=1021
--
Alexey
Re: [general] Lesson and roadmap thoughts
Posted by Tim Ellison <t....@gmail.com>.
Sean Qiu wrote:
> 2009/4/20 Tim Ellison <t....@gmail.com>:
>> Alexei Fedotov wrote:
>>> Under resource constraints we may even think of dropping Java 5 in favor of
>>> Java 6. This would save Java 6 supporters their merge efforts and nullify
>>> merge bugs.
>> Maybe. I hadn't thought of going that far - at least, not without a
>> reasonable overlap period that allows people to migrate from 5.0 to 6.0
>> stream.
>>
>> Given we don't make a big deal of publishing the 6.0 stream code today,
>> I think it would be unreasonable to abandon the 5.0 stream abruptly. We
>> may well get to that point over time.
>>
>>> Why have not we done that before? AFAIK, one wanted to pass TCK for Java 5,
>>> and that was an important step to ship Harmony release, which in turn was
>>> important to officially participate in benchmarks. I don't think this plan
>>> would fail due to 5% more failures we got due to Java version
>>> incompatibilities. There are stronger risks, e.g. TCK absence.
>> I agree, and that is why I'm proposing a different approach for the 6.0
>> stream. Rather than shoot for 100% completeness to the Java SE 6.0 API
>> and request that TCK, I suggest we select a number of Harmony modules
>> and publish a useful 'select' runtime. With our architecture it is then
>> trivial to expand out with the additional modules to reach the full SE
>> in time.
>>
>
> Interesting.
>
> Then from whose point of view that we should focus on?
> How should we define the "selected" modules ?
Good questions. Let's talk details on a separate thread.
> Maybe we can discuss it by details to meet the goal which could and
> should be customer or user oriented.
If we were being trendy we'd target the "cloud computing" users, which
has the added advantage of being anything we want it to be ;-)
Regards,
Tim
Re: [general] Lesson and roadmap thoughts
Posted by Sean Qiu <se...@gmail.com>.
2009/4/20 Tim Ellison <t....@gmail.com>:
> Alexei Fedotov wrote:
>> Under resource constraints we may even think of dropping Java 5 in favor of
>> Java 6. This would save Java 6 supporters their merge efforts and nullify
>> merge bugs.
>
> Maybe. I hadn't thought of going that far - at least, not without a
> reasonable overlap period that allows people to migrate from 5.0 to 6.0
> stream.
>
> Given we don't make a big deal of publishing the 6.0 stream code today,
> I think it would be unreasonable to abandon the 5.0 stream abruptly. We
> may well get to that point over time.
>
>> Why have not we done that before? AFAIK, one wanted to pass TCK for Java 5,
>> and that was an important step to ship Harmony release, which in turn was
>> important to officially participate in benchmarks. I don't think this plan
>> would fail due to 5% more failures we got due to Java version
>> incompatibilities. There are stronger risks, e.g. TCK absence.
>
> I agree, and that is why I'm proposing a different approach for the 6.0
> stream. Rather than shoot for 100% completeness to the Java SE 6.0 API
> and request that TCK, I suggest we select a number of Harmony modules
> and publish a useful 'select' runtime. With our architecture it is then
> trivial to expand out with the additional modules to reach the full SE
> in time.
>
Interesting.
Then from whose point of view that we should focus on?
How should we define the "selected" modules ?
Maybe we can discuss it by details to meet the goal which could and
should be customer or user oriented.
> Regards,
> Tim
>
>> On Fri, Apr 17, 2009 at 6:12 PM, Tim Ellison <t....@gmail.com> wrote:
>>
>>> Sian January wrote:
>>>> I agree that we need to be more timely about the next milestone.
>>>>
>>>> It would also be good to focus a bit more on Java 6 since Java 5 is
>>>> starting to become old. Maybe we could do a Java 6 M1 (or subset as
>>>> you describe) to coincide with Java 5 M10?
>>> I'm not too bothered about the 'age' of Java 5. IMHO there are not too
>>> may apps that have a hard dependency on Java 6 APIs yet; but we have got
>>> some technology in that branch that, at the moment, does not see the
>>> light of day and that is a shame.
>>>
>>>> On another note, I would also like to see us get up to 100% pass rate
>>>> for the class library tests and then keep this going - i.e. if a
>>>> commit causes any tests to fail then it should be fixed asap or backed
>>>> out. I think this would have helped us avoid some of the issues that
>>>> caused such a long stabilisation period for M9.
>>> Agreed. Having build/test systems visible in the ASF infrastructure
>>> would help. There has been some discussion about getting separable
>>> tests, but even if that does not come about we could extend Hudson to do
>>> a full build/test cycle too.
>>>
>>> I expect that we will have problems getting platform coverage from the
>>> ASF Hudson systems though. AFAIK they are all Linux x86_64 machines.
>>>
>>> Regards,
>>> Tim
>>>
>>>> 2009/4/17 Tim Ellison <t....@gmail.com>:
>>>>> Immediately after a release is usually the time that I'm thinking about
>>>>> lessons learned, the project road map, and future deliveries from
>>> Harmony.
>>>>> Most noticeable for me was the long stabilization period we undertook
>>>>> for M9 compared to earlier releases. This was required, I believe,
>>>>> because of the longer open development period [1]. The lesson to take
>>>>> away from that is to ensure we keep an eye on our regular release
>>>>> schedule and keep the time boxes short enough that stable fixes get out
>>>>> to our users, and we minimize the frozen codebase period.
>>>>>
>>>>> Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
>>>>> May (6 weeks after April 8th = May 20).
>>>>>
>>>>>
>>>>> The other thing that bothers me is the lack of expose we give our Java 6
>>>>> branch. While the majority of fixes we commit are applied to both
>>>>> branches, we have some good work completed in the Java 6 API branch's
>>>>> core classes that is not getting the uptake it deserves.
>>>>>
>>>>> The non-core Java 6 classes get very little attention at the moment.
>>>>> With Harmony's strong modular architecture we can easily construct a
>>>>> headless runtime that delivers those core classes without the missing
>>>>> functionality.
>>>>>
>>>>> I'd like to suggest that we experiment with the flexible components in
>>>>> Harmony to deliver a headless runtime based on the Java 6 APIs.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> [1] Depending on exactly how you count it, we were open from 17 Nov - 27
>>>>> Feb, which is a massive 14.5 weeks!
>>>>>
>>>>> Regards,
>>>>> Tim
>>>>>
>>>>
>>>>
>>
>>
>>
>
--
Best Regards
Sean, Xiao Xia Qiu
Re: [general] Lesson and roadmap thoughts
Posted by Tony Wu <wu...@gmail.com>.
2009/4/20 Tim Ellison <t....@gmail.com>:
> Alexei Fedotov wrote:
>> Under resource constraints we may even think of dropping Java 5 in favor of
>> Java 6. This would save Java 6 supporters their merge efforts and nullify
>> merge bugs.
>
> Maybe. I hadn't thought of going that far - at least, not without a
> reasonable overlap period that allows people to migrate from 5.0 to 6.0
> stream.
>
> Given we don't make a big deal of publishing the 6.0 stream code today,
> I think it would be unreasonable to abandon the 5.0 stream abruptly. We
> may well get to that point over time.
>
>> Why have not we done that before? AFAIK, one wanted to pass TCK for Java 5,
>> and that was an important step to ship Harmony release, which in turn was
>> important to officially participate in benchmarks. I don't think this plan
>> would fail due to 5% more failures we got due to Java version
>> incompatibilities. There are stronger risks, e.g. TCK absence.
>
> I agree, and that is why I'm proposing a different approach for the 6.0
> stream. Rather than shoot for 100% completeness to the Java SE 6.0 API
> and request that TCK, I suggest we select a number of Harmony modules
> and publish a useful 'select' runtime. With our architecture it is then
> trivial to expand out with the additional modules to reach the full SE
> in time.
>
Good thoughts. A minimal core of the runtime at 6.0 level is easier to
achieve - it brings less effort than delivering the whole Java6. And
then the other modules could be added in on demand when they are
ready. I believe it is also a good experiment on modulization.
Besides that, one of our GSOC project is the OSGi on Harmony, maybe we
can think about building this core runtime on OSGi.
> Regards,
> Tim
>
>> On Fri, Apr 17, 2009 at 6:12 PM, Tim Ellison <t....@gmail.com> wrote:
>>
>>> Sian January wrote:
>>>> I agree that we need to be more timely about the next milestone.
>>>>
>>>> It would also be good to focus a bit more on Java 6 since Java 5 is
>>>> starting to become old. Maybe we could do a Java 6 M1 (or subset as
>>>> you describe) to coincide with Java 5 M10?
>>> I'm not too bothered about the 'age' of Java 5. IMHO there are not too
>>> may apps that have a hard dependency on Java 6 APIs yet; but we have got
>>> some technology in that branch that, at the moment, does not see the
>>> light of day and that is a shame.
>>>
>>>> On another note, I would also like to see us get up to 100% pass rate
>>>> for the class library tests and then keep this going - i.e. if a
>>>> commit causes any tests to fail then it should be fixed asap or backed
>>>> out. I think this would have helped us avoid some of the issues that
>>>> caused such a long stabilisation period for M9.
>>> Agreed. Having build/test systems visible in the ASF infrastructure
>>> would help. There has been some discussion about getting separable
>>> tests, but even if that does not come about we could extend Hudson to do
>>> a full build/test cycle too.
>>>
>>> I expect that we will have problems getting platform coverage from the
>>> ASF Hudson systems though. AFAIK they are all Linux x86_64 machines.
>>>
>>> Regards,
>>> Tim
>>>
>>>> 2009/4/17 Tim Ellison <t....@gmail.com>:
>>>>> Immediately after a release is usually the time that I'm thinking about
>>>>> lessons learned, the project road map, and future deliveries from
>>> Harmony.
>>>>> Most noticeable for me was the long stabilization period we undertook
>>>>> for M9 compared to earlier releases. This was required, I believe,
>>>>> because of the longer open development period [1]. The lesson to take
>>>>> away from that is to ensure we keep an eye on our regular release
>>>>> schedule and keep the time boxes short enough that stable fixes get out
>>>>> to our users, and we minimize the frozen codebase period.
>>>>>
>>>>> Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
>>>>> May (6 weeks after April 8th = May 20).
>>>>>
>>>>>
>>>>> The other thing that bothers me is the lack of expose we give our Java 6
>>>>> branch. While the majority of fixes we commit are applied to both
>>>>> branches, we have some good work completed in the Java 6 API branch's
>>>>> core classes that is not getting the uptake it deserves.
>>>>>
>>>>> The non-core Java 6 classes get very little attention at the moment.
>>>>> With Harmony's strong modular architecture we can easily construct a
>>>>> headless runtime that delivers those core classes without the missing
>>>>> functionality.
>>>>>
>>>>> I'd like to suggest that we experiment with the flexible components in
>>>>> Harmony to deliver a headless runtime based on the Java 6 APIs.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> [1] Depending on exactly how you count it, we were open from 17 Nov - 27
>>>>> Feb, which is a massive 14.5 weeks!
>>>>>
>>>>> Regards,
>>>>> Tim
>>>>>
>>>>
>>>>
>>
>>
>>
>
--
Tony Wu
China Software Development Lab, IBM
Re: [general] Lesson and roadmap thoughts
Posted by Tim Ellison <t....@gmail.com>.
Alexei Fedotov wrote:
> Under resource constraints we may even think of dropping Java 5 in favor of
> Java 6. This would save Java 6 supporters their merge efforts and nullify
> merge bugs.
Maybe. I hadn't thought of going that far - at least, not without a
reasonable overlap period that allows people to migrate from 5.0 to 6.0
stream.
Given we don't make a big deal of publishing the 6.0 stream code today,
I think it would be unreasonable to abandon the 5.0 stream abruptly. We
may well get to that point over time.
> Why have not we done that before? AFAIK, one wanted to pass TCK for Java 5,
> and that was an important step to ship Harmony release, which in turn was
> important to officially participate in benchmarks. I don't think this plan
> would fail due to 5% more failures we got due to Java version
> incompatibilities. There are stronger risks, e.g. TCK absence.
I agree, and that is why I'm proposing a different approach for the 6.0
stream. Rather than shoot for 100% completeness to the Java SE 6.0 API
and request that TCK, I suggest we select a number of Harmony modules
and publish a useful 'select' runtime. With our architecture it is then
trivial to expand out with the additional modules to reach the full SE
in time.
Regards,
Tim
> On Fri, Apr 17, 2009 at 6:12 PM, Tim Ellison <t....@gmail.com> wrote:
>
>> Sian January wrote:
>>> I agree that we need to be more timely about the next milestone.
>>>
>>> It would also be good to focus a bit more on Java 6 since Java 5 is
>>> starting to become old. Maybe we could do a Java 6 M1 (or subset as
>>> you describe) to coincide with Java 5 M10?
>> I'm not too bothered about the 'age' of Java 5. IMHO there are not too
>> may apps that have a hard dependency on Java 6 APIs yet; but we have got
>> some technology in that branch that, at the moment, does not see the
>> light of day and that is a shame.
>>
>>> On another note, I would also like to see us get up to 100% pass rate
>>> for the class library tests and then keep this going - i.e. if a
>>> commit causes any tests to fail then it should be fixed asap or backed
>>> out. I think this would have helped us avoid some of the issues that
>>> caused such a long stabilisation period for M9.
>> Agreed. Having build/test systems visible in the ASF infrastructure
>> would help. There has been some discussion about getting separable
>> tests, but even if that does not come about we could extend Hudson to do
>> a full build/test cycle too.
>>
>> I expect that we will have problems getting platform coverage from the
>> ASF Hudson systems though. AFAIK they are all Linux x86_64 machines.
>>
>> Regards,
>> Tim
>>
>>> 2009/4/17 Tim Ellison <t....@gmail.com>:
>>>> Immediately after a release is usually the time that I'm thinking about
>>>> lessons learned, the project road map, and future deliveries from
>> Harmony.
>>>> Most noticeable for me was the long stabilization period we undertook
>>>> for M9 compared to earlier releases. This was required, I believe,
>>>> because of the longer open development period [1]. The lesson to take
>>>> away from that is to ensure we keep an eye on our regular release
>>>> schedule and keep the time boxes short enough that stable fixes get out
>>>> to our users, and we minimize the frozen codebase period.
>>>>
>>>> Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
>>>> May (6 weeks after April 8th = May 20).
>>>>
>>>>
>>>> The other thing that bothers me is the lack of expose we give our Java 6
>>>> branch. While the majority of fixes we commit are applied to both
>>>> branches, we have some good work completed in the Java 6 API branch's
>>>> core classes that is not getting the uptake it deserves.
>>>>
>>>> The non-core Java 6 classes get very little attention at the moment.
>>>> With Harmony's strong modular architecture we can easily construct a
>>>> headless runtime that delivers those core classes without the missing
>>>> functionality.
>>>>
>>>> I'd like to suggest that we experiment with the flexible components in
>>>> Harmony to deliver a headless runtime based on the Java 6 APIs.
>>>>
>>>> Thoughts?
>>>>
>>>> [1] Depending on exactly how you count it, we were open from 17 Nov - 27
>>>> Feb, which is a massive 14.5 weeks!
>>>>
>>>> Regards,
>>>> Tim
>>>>
>>>
>>>
>
>
>
Re: [general] Lesson and roadmap thoughts
Posted by Alexei Fedotov <al...@gmail.com>.
Hello,
Under resource constraints we may even think of dropping Java 5 in favor of
Java 6. This would save Java 6 supporters their merge efforts and nullify
merge bugs.
Why have not we done that before? AFAIK, one wanted to pass TCK for Java 5,
and that was an important step to ship Harmony release, which in turn was
important to officially participate in benchmarks. I don't think this plan
would fail due to 5% more failures we got due to Java version
incompatibilities. There are stronger risks, e.g. TCK absence.
Thanks.
On Fri, Apr 17, 2009 at 6:12 PM, Tim Ellison <t....@gmail.com> wrote:
> Sian January wrote:
> > I agree that we need to be more timely about the next milestone.
> >
> > It would also be good to focus a bit more on Java 6 since Java 5 is
> > starting to become old. Maybe we could do a Java 6 M1 (or subset as
> > you describe) to coincide with Java 5 M10?
>
> I'm not too bothered about the 'age' of Java 5. IMHO there are not too
> may apps that have a hard dependency on Java 6 APIs yet; but we have got
> some technology in that branch that, at the moment, does not see the
> light of day and that is a shame.
>
> > On another note, I would also like to see us get up to 100% pass rate
> > for the class library tests and then keep this going - i.e. if a
> > commit causes any tests to fail then it should be fixed asap or backed
> > out. I think this would have helped us avoid some of the issues that
> > caused such a long stabilisation period for M9.
>
> Agreed. Having build/test systems visible in the ASF infrastructure
> would help. There has been some discussion about getting separable
> tests, but even if that does not come about we could extend Hudson to do
> a full build/test cycle too.
>
> I expect that we will have problems getting platform coverage from the
> ASF Hudson systems though. AFAIK they are all Linux x86_64 machines.
>
> Regards,
> Tim
>
> > 2009/4/17 Tim Ellison <t....@gmail.com>:
> >> Immediately after a release is usually the time that I'm thinking about
> >> lessons learned, the project road map, and future deliveries from
> Harmony.
> >>
> >> Most noticeable for me was the long stabilization period we undertook
> >> for M9 compared to earlier releases. This was required, I believe,
> >> because of the longer open development period [1]. The lesson to take
> >> away from that is to ensure we keep an eye on our regular release
> >> schedule and keep the time boxes short enough that stable fixes get out
> >> to our users, and we minimize the frozen codebase period.
> >>
> >> Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
> >> May (6 weeks after April 8th = May 20).
> >>
> >>
> >> The other thing that bothers me is the lack of expose we give our Java 6
> >> branch. While the majority of fixes we commit are applied to both
> >> branches, we have some good work completed in the Java 6 API branch's
> >> core classes that is not getting the uptake it deserves.
> >>
> >> The non-core Java 6 classes get very little attention at the moment.
> >> With Harmony's strong modular architecture we can easily construct a
> >> headless runtime that delivers those core classes without the missing
> >> functionality.
> >>
> >> I'd like to suggest that we experiment with the flexible components in
> >> Harmony to deliver a headless runtime based on the Java 6 APIs.
> >>
> >> Thoughts?
> >>
> >> [1] Depending on exactly how you count it, we were open from 17 Nov - 27
> >> Feb, which is a massive 14.5 weeks!
> >>
> >> Regards,
> >> Tim
> >>
> >
> >
> >
>
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://www.telecom-express.ru/
http://people.apache.org/~aaf/
http://harmony.apache.org/
http://code.google.com/p/openmeetings/
Re: [general] Lesson and roadmap thoughts
Posted by Tim Ellison <t....@gmail.com>.
Sian January wrote:
> I agree that we need to be more timely about the next milestone.
>
> It would also be good to focus a bit more on Java 6 since Java 5 is
> starting to become old. Maybe we could do a Java 6 M1 (or subset as
> you describe) to coincide with Java 5 M10?
I'm not too bothered about the 'age' of Java 5. IMHO there are not too
may apps that have a hard dependency on Java 6 APIs yet; but we have got
some technology in that branch that, at the moment, does not see the
light of day and that is a shame.
> On another note, I would also like to see us get up to 100% pass rate
> for the class library tests and then keep this going - i.e. if a
> commit causes any tests to fail then it should be fixed asap or backed
> out. I think this would have helped us avoid some of the issues that
> caused such a long stabilisation period for M9.
Agreed. Having build/test systems visible in the ASF infrastructure
would help. There has been some discussion about getting separable
tests, but even if that does not come about we could extend Hudson to do
a full build/test cycle too.
I expect that we will have problems getting platform coverage from the
ASF Hudson systems though. AFAIK they are all Linux x86_64 machines.
Regards,
Tim
> 2009/4/17 Tim Ellison <t....@gmail.com>:
>> Immediately after a release is usually the time that I'm thinking about
>> lessons learned, the project road map, and future deliveries from Harmony.
>>
>> Most noticeable for me was the long stabilization period we undertook
>> for M9 compared to earlier releases. This was required, I believe,
>> because of the longer open development period [1]. The lesson to take
>> away from that is to ensure we keep an eye on our regular release
>> schedule and keep the time boxes short enough that stable fixes get out
>> to our users, and we minimize the frozen codebase period.
>>
>> Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
>> May (6 weeks after April 8th = May 20).
>>
>>
>> The other thing that bothers me is the lack of expose we give our Java 6
>> branch. While the majority of fixes we commit are applied to both
>> branches, we have some good work completed in the Java 6 API branch's
>> core classes that is not getting the uptake it deserves.
>>
>> The non-core Java 6 classes get very little attention at the moment.
>> With Harmony's strong modular architecture we can easily construct a
>> headless runtime that delivers those core classes without the missing
>> functionality.
>>
>> I'd like to suggest that we experiment with the flexible components in
>> Harmony to deliver a headless runtime based on the Java 6 APIs.
>>
>> Thoughts?
>>
>> [1] Depending on exactly how you count it, we were open from 17 Nov - 27
>> Feb, which is a massive 14.5 weeks!
>>
>> Regards,
>> Tim
>>
>
>
>
Re: [general] Lesson and roadmap thoughts
Posted by Sian January <si...@googlemail.com>.
Hi Tim,
I agree that we need to be more timely about the next milestone.
It would also be good to focus a bit more on Java 6 since Java 5 is
starting to become old. Maybe we could do a Java 6 M1 (or subset as
you describe) to coincide with Java 5 M10?
On another note, I would also like to see us get up to 100% pass rate
for the class library tests and then keep this going - i.e. if a
commit causes any tests to fail then it should be fixed asap or backed
out. I think this would have helped us avoid some of the issues that
caused such a long stabilisation period for M9.
Sian
2009/4/17 Tim Ellison <t....@gmail.com>:
> Immediately after a release is usually the time that I'm thinking about
> lessons learned, the project road map, and future deliveries from Harmony.
>
> Most noticeable for me was the long stabilization period we undertook
> for M9 compared to earlier releases. This was required, I believe,
> because of the longer open development period [1]. The lesson to take
> away from that is to ensure we keep an eye on our regular release
> schedule and keep the time boxes short enough that stable fixes get out
> to our users, and we minimize the frozen codebase period.
>
> Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
> May (6 weeks after April 8th = May 20).
>
>
> The other thing that bothers me is the lack of expose we give our Java 6
> branch. While the majority of fixes we commit are applied to both
> branches, we have some good work completed in the Java 6 API branch's
> core classes that is not getting the uptake it deserves.
>
> The non-core Java 6 classes get very little attention at the moment.
> With Harmony's strong modular architecture we can easily construct a
> headless runtime that delivers those core classes without the missing
> functionality.
>
> I'd like to suggest that we experiment with the flexible components in
> Harmony to deliver a headless runtime based on the Java 6 APIs.
>
> Thoughts?
>
> [1] Depending on exactly how you count it, we were open from 17 Nov - 27
> Feb, which is a massive 14.5 weeks!
>
> Regards,
> Tim
>
--
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Re: [general] Lesson and roadmap thoughts
Posted by Xiao-Feng Li <xi...@gmail.com>.
Agree to have Java 6 runtime experimented.
Thanks,
xiaofeng
On Fri, Apr 17, 2009 at 7:23 PM, Tim Ellison <t....@gmail.com> wrote:
> Immediately after a release is usually the time that I'm thinking about
> lessons learned, the project road map, and future deliveries from Harmony.
>
> Most noticeable for me was the long stabilization period we undertook
> for M9 compared to earlier releases. This was required, I believe,
> because of the longer open development period [1]. The lesson to take
> away from that is to ensure we keep an eye on our regular release
> schedule and keep the time boxes short enough that stable fixes get out
> to our users, and we minimize the frozen codebase period.
>
> Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
> May (6 weeks after April 8th = May 20).
>
>
> The other thing that bothers me is the lack of expose we give our Java 6
> branch. While the majority of fixes we commit are applied to both
> branches, we have some good work completed in the Java 6 API branch's
> core classes that is not getting the uptake it deserves.
>
> The non-core Java 6 classes get very little attention at the moment.
> With Harmony's strong modular architecture we can easily construct a
> headless runtime that delivers those core classes without the missing
> functionality.
>
> I'd like to suggest that we experiment with the flexible components in
> Harmony to deliver a headless runtime based on the Java 6 APIs.
>
> Thoughts?
>
> [1] Depending on exactly how you count it, we were open from 17 Nov - 27
> Feb, which is a massive 14.5 weeks!
>
> Regards,
> Tim
>
--
http://people.apache.org/~xli
Re: [general] Lesson and roadmap thoughts
Posted by Tim Ellison <t....@gmail.com>.
Nathan Beyer wrote:
> I would like to help with the merging, but I don't feel like I
> understand our current conventions for doing it. Would some one mind
> documenting the why, what and how? This would help me get in the flow
> and make it a habit.
>
> I feel like this is the problem as the integrity builds - it isn't
> documented, so it requires research and reverse-engineering to repeat by
> another person.
Let me move that to a different thread...
Tim
> On Apr 21, 2009, at 11:04 AM, Sean Qiu <se...@gmail.com> wrote:
>
>> 2009/4/17 Tim Ellison <t....@gmail.com>:
>>> Immediately after a release is usually the time that I'm thinking about
>>> lessons learned, the project road map, and future deliveries from
>>> Harmony.
>>>
>>> Most noticeable for me was the long stabilization period we undertook
>>> for M9 compared to earlier releases. This was required, I believe,
>>> because of the longer open development period [1]. The lesson to take
>>> away from that is to ensure we keep an eye on our regular release
>>> schedule and keep the time boxes short enough that stable fixes get out
>>> to our users, and we minimize the frozen codebase period.
>>>
>>> Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
>>> May (6 weeks after April 8th = May 20).
>>>
>>>
>>> The other thing that bothers me is the lack of expose we give our Java 6
>>> branch. While the majority of fixes we commit are applied to both
>>> branches, we have some good work completed in the Java 6 API branch's
>>> core classes that is not getting the uptake it deserves.
>>
>> What about each committer takes charge of this?
>> When we apply certain patches to trunk,
>> we'd make the decision whether merge it to branch 6 meanwhile.
>>
>> I've tried to do some merging work, it is not easy to tell "proper"
>> and "improper" against a great number of patches.
>> It do introduce potential risks while merging.
>>
>>>
>>> The non-core Java 6 classes get very little attention at the moment.
>>> With Harmony's strong modular architecture we can easily construct a
>>> headless runtime that delivers those core classes without the missing
>>> functionality.
>>>
>>> I'd like to suggest that we experiment with the flexible components in
>>> Harmony to deliver a headless runtime based on the Java 6 APIs.
>>>
>>
>> +1
>>
>>> Thoughts?
>>>
>>> [1] Depending on exactly how you count it, we were open from 17 Nov - 27
>>> Feb, which is a massive 14.5 weeks!
>>>
>>> Regards,
>>> Tim
>>>
>>
>>
>>
>> --
>> Best Regards
>> Sean, Xiao Xia Qiu
>
Re: [general] Lesson and roadmap thoughts
Posted by Tim Ellison <t....@gmail.com>.
Sean Qiu wrote:
> I'm not making a complaint, I'd like to take this job in fact. :-)
>
> What I mean here is maybe we can commit patch to both trunk and Java 6
> branch at the same time.
> (It may bring more workload to every committer.)
>
> Merging by bunch is convenient but error-prone.
Sure, I see.
Thanks,
Tim
Re: [general] Lesson and roadmap thoughts
Posted by Sean Qiu <se...@gmail.com>.
I'm not making a complaint, I'd like to take this job in fact. :-)
What I mean here is maybe we can commit patch to both trunk and Java 6
branch at the same time.
(It may bring more workload to every committer.)
Merging by bunch is convenient but error-prone.
2009/4/22 Nathan Beyer <nb...@gmail.com>:
> I would like to help with the merging, but I don't feel like I understand
> our current conventions for doing it. Would some one mind documenting the
> why, what and how? This would help me get in the flow and make it a habit.
>
> I feel like this is the problem as the integrity builds - it isn't
> documented, so it requires research and reverse-engineering to repeat by
> another person.
>
> Sent from my iPhone
>
> On Apr 21, 2009, at 11:04 AM, Sean Qiu <se...@gmail.com> wrote:
>
>> 2009/4/17 Tim Ellison <t....@gmail.com>:
>>>
>>> Immediately after a release is usually the time that I'm thinking about
>>> lessons learned, the project road map, and future deliveries from
>>> Harmony.
>>>
>>> Most noticeable for me was the long stabilization period we undertook
>>> for M9 compared to earlier releases. This was required, I believe,
>>> because of the longer open development period [1]. The lesson to take
>>> away from that is to ensure we keep an eye on our regular release
>>> schedule and keep the time boxes short enough that stable fixes get out
>>> to our users, and we minimize the frozen codebase period.
>>>
>>> Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
>>> May (6 weeks after April 8th = May 20).
>>>
>>>
>>> The other thing that bothers me is the lack of expose we give our Java 6
>>> branch. While the majority of fixes we commit are applied to both
>>> branches, we have some good work completed in the Java 6 API branch's
>>> core classes that is not getting the uptake it deserves.
>>
>> What about each committer takes charge of this?
>> When we apply certain patches to trunk,
>> we'd make the decision whether merge it to branch 6 meanwhile.
>>
>> I've tried to do some merging work, it is not easy to tell "proper"
>> and "improper" against a great number of patches.
>> It do introduce potential risks while merging.
>>
>>>
>>> The non-core Java 6 classes get very little attention at the moment.
>>> With Harmony's strong modular architecture we can easily construct a
>>> headless runtime that delivers those core classes without the missing
>>> functionality.
>>>
>>> I'd like to suggest that we experiment with the flexible components in
>>> Harmony to deliver a headless runtime based on the Java 6 APIs.
>>>
>>
>> +1
>>
>>> Thoughts?
>>>
>>> [1] Depending on exactly how you count it, we were open from 17 Nov - 27
>>> Feb, which is a massive 14.5 weeks!
>>>
>>> Regards,
>>> Tim
>>>
>>
>>
>>
>> --
>> Best Regards
>> Sean, Xiao Xia Qiu
>
--
Best Regards
Sean, Xiao Xia Qiu
Re: [general] Lesson and roadmap thoughts
Posted by Nathan Beyer <nb...@gmail.com>.
I would like to help with the merging, but I don't feel like I
understand our current conventions for doing it. Would some one mind
documenting the why, what and how? This would help me get in the flow
and make it a habit.
I feel like this is the problem as the integrity builds - it isn't
documented, so it requires research and reverse-engineering to repeat
by another person.
Sent from my iPhone
On Apr 21, 2009, at 11:04 AM, Sean Qiu <se...@gmail.com> wrote:
> 2009/4/17 Tim Ellison <t....@gmail.com>:
>> Immediately after a release is usually the time that I'm thinking
>> about
>> lessons learned, the project road map, and future deliveries from
>> Harmony.
>>
>> Most noticeable for me was the long stabilization period we undertook
>> for M9 compared to earlier releases. This was required, I believe,
>> because of the longer open development period [1]. The lesson to
>> take
>> away from that is to ensure we keep an eye on our regular release
>> schedule and keep the time boxes short enough that stable fixes get
>> out
>> to our users, and we minimize the frozen codebase period.
>>
>> Looking ahead I'd therefore expect 5.0 M10 to be released at the
>> end of
>> May (6 weeks after April 8th = May 20).
>>
>>
>> The other thing that bothers me is the lack of expose we give our
>> Java 6
>> branch. While the majority of fixes we commit are applied to both
>> branches, we have some good work completed in the Java 6 API branch's
>> core classes that is not getting the uptake it deserves.
>
> What about each committer takes charge of this?
> When we apply certain patches to trunk,
> we'd make the decision whether merge it to branch 6 meanwhile.
>
> I've tried to do some merging work, it is not easy to tell "proper"
> and "improper" against a great number of patches.
> It do introduce potential risks while merging.
>
>>
>> The non-core Java 6 classes get very little attention at the moment.
>> With Harmony's strong modular architecture we can easily construct a
>> headless runtime that delivers those core classes without the missing
>> functionality.
>>
>> I'd like to suggest that we experiment with the flexible components
>> in
>> Harmony to deliver a headless runtime based on the Java 6 APIs.
>>
>
> +1
>
>> Thoughts?
>>
>> [1] Depending on exactly how you count it, we were open from 17 Nov
>> - 27
>> Feb, which is a massive 14.5 weeks!
>>
>> Regards,
>> Tim
>>
>
>
>
> --
> Best Regards
> Sean, Xiao Xia Qiu
Re: [general] Lesson and roadmap thoughts
Posted by Sean Qiu <se...@gmail.com>.
Yes
2009/4/22 Tim Ellison <t....@gmail.com>:
> Sean Qiu wrote:
>> What about each committer takes charge of this?
>> When we apply certain patches to trunk,
>> we'd make the decision whether merge it to branch 6 meanwhile.
>
> Just to be clear that I understand your suggestion, you mean on each
> commit the developer does the merge "there and then"?
>
> Regards,
> Tim
>
>> I've tried to do some merging work, it is not easy to tell "proper"
>> and "improper" against a great number of patches.
>> It do introduce potential risks while merging.
>
>
--
Best Regards
Sean, Xiao Xia Qiu
Re: [general] Lesson and roadmap thoughts
Posted by Tim Ellison <t....@gmail.com>.
Sean Qiu wrote:
> What about each committer takes charge of this?
> When we apply certain patches to trunk,
> we'd make the decision whether merge it to branch 6 meanwhile.
Just to be clear that I understand your suggestion, you mean on each
commit the developer does the merge "there and then"?
Regards,
Tim
> I've tried to do some merging work, it is not easy to tell "proper"
> and "improper" against a great number of patches.
> It do introduce potential risks while merging.
Re: [general] Lesson and roadmap thoughts
Posted by Sean Qiu <se...@gmail.com>.
2009/4/17 Tim Ellison <t....@gmail.com>:
> Immediately after a release is usually the time that I'm thinking about
> lessons learned, the project road map, and future deliveries from Harmony.
>
> Most noticeable for me was the long stabilization period we undertook
> for M9 compared to earlier releases. This was required, I believe,
> because of the longer open development period [1]. The lesson to take
> away from that is to ensure we keep an eye on our regular release
> schedule and keep the time boxes short enough that stable fixes get out
> to our users, and we minimize the frozen codebase period.
>
> Looking ahead I'd therefore expect 5.0 M10 to be released at the end of
> May (6 weeks after April 8th = May 20).
>
>
> The other thing that bothers me is the lack of expose we give our Java 6
> branch. While the majority of fixes we commit are applied to both
> branches, we have some good work completed in the Java 6 API branch's
> core classes that is not getting the uptake it deserves.
What about each committer takes charge of this?
When we apply certain patches to trunk,
we'd make the decision whether merge it to branch 6 meanwhile.
I've tried to do some merging work, it is not easy to tell "proper"
and "improper" against a great number of patches.
It do introduce potential risks while merging.
>
> The non-core Java 6 classes get very little attention at the moment.
> With Harmony's strong modular architecture we can easily construct a
> headless runtime that delivers those core classes without the missing
> functionality.
>
> I'd like to suggest that we experiment with the flexible components in
> Harmony to deliver a headless runtime based on the Java 6 APIs.
>
+1
> Thoughts?
>
> [1] Depending on exactly how you count it, we were open from 17 Nov - 27
> Feb, which is a massive 14.5 weeks!
>
> Regards,
> Tim
>
--
Best Regards
Sean, Xiao Xia Qiu