Denis Kishenko wrote:
Most of wiki "module" pages were updated last time several months ago.
Do they have actual information?
It is easier for Wiki to be out-dated, that's why it needs to be taken
care of more:). Specific for the "module" page, AFAIK, the 5.0 bring up
work on many modules are a
Most of wiki "module" pages were updated last time several months ago.
Do they have actual information?
2006/9/13, Paulex Yang <[EMAIL PROTECTED]>:
Discussion on dev-list is generally first choice, I totally agree with
that. Wiki is just supplement to record somewhat significant work needs
longe
Denis Kishenko wrote:
If I am going to work with whole module then "Harmony class library
development status"[1] page is useful but if I want to work with
several classes, for example fix some JAPI issues or make serious
changes, then existing wiki page can't be used.
Anyone can create detail pag
If I am going to work with whole module then "Harmony class library
development status"[1] page is useful but if I want to work with
several classes, for example fix some JAPI issues or make serious
changes, then existing wiki page can't be used.
I agree with creating JIRA issue and sending notif
Rana Dasgupta wrote:
Does this apply to bug fixes as well? For significant fixes that have an
architectural impact, certainly we need to inform the dev list,
specially if
there has been some discussion already. But for more local fixes, is it
enough to add a comment to the issue on JIRA, stat
Does this apply to bug fixes as well? For significant fixes that have an
architectural impact, certainly we need to inform the dev list, specially if
there has been some discussion already. But for more local fixes, is it
enough to add a comment to the issue on JIRA, stating current ownership, and
On Wed, Sep 06, 2006 at 07:43:59PM +0400, Oleg Khaschansky wrote:
> There were situations when several people started work on the same
> issue simultaneously. This happens because it is impossible to assign
> an issue to a non-committer.
Its probably possible to create a group
harmony-contribut
but again, I'll emphasize that you want to bring this to the dev list.
Adding to a wiki or a JIRA is very "silent" compared to an introduction
and discussion :)
geir
Paulex Yang wrote:
Geir Magnusson Jr. wrote:
Good.
Also, don't just do things in JIRA. Add the comment in JIRA, but also
s
>-Original Message-
>From: Paulex Yang [mailto:[EMAIL PROTECTED]
>Sent: Thursday, September 07, 2006 12:38 PM
>To: harmony-dev@incubator.apache.org
>Subject: Re: [general] Marking JIRA issues before creation of patches.
>
>Geir Magnusson Jr. wrote:
>> Good.
>&
Geir Magnusson Jr. wrote:
Good.
Also, don't just do things in JIRA. Add the comment in JIRA, but also
send something to the dev list. That way, people who are interested
will more easily notice and maybe offer to help, or such...
+1, and for classlib, we have had some wiki pages[1]-[3] to li
Good.
Also, don't just do things in JIRA. Add the comment in JIRA, but also
send something to the dev list. That way, people who are interested
will more easily notice and maybe offer to help, or such...
geir
Oleg Khaschansky wrote:
Hi all,
There were situations when several people star
Hi all,
There were situations when several people started work on the same
issue simultaneously. This happens because it is impossible to assign
an issue to a non-committer. I suggest the following process to
prevent these collisions:
1. If non-committer starts investigation and is pretty sure t
12 matches
Mail list logo
