Hi Aliya,
many thanks, your answer is very clear.
As soon I have an example ready I will send to you, but for now your answer
is enough for me.
Many thanks againd an Best Regards
"Aliya Walji"
<[EMAIL PROTECTED]
undation.org> To
Sent by: Roberto
mifos-developer-b Musso/Ireland/Contr/[EMAIL PROTECTED]
[EMAIL PROTECTED] cc
ceforge.net Developer
<[EMAIL PROTECTED]
net>
02/22/2008 05:47 Subject
PM Re: [Mifos-developer] About
IssueTracker
Please respond to
Developer
<mifos-developer@
lists.sourceforge
.net>
Hi Roberto,
I want to clarify your question so I understand better which scenario
for which you are trying to determine process.
Are you referring to cases where you have a design proposal for a piece
of code or functionality that you are building and you want feedback on
this? In general, for cases where you have done an analysis or written
a proposal, the best place to send this is to the developer mailing
list. If there is an item in the issue tracker associated with your
analysis/document, you can also additionally attach your documents to
the issue tracker item (but still email the listserv with a request to
have the information reviewed).
If you do not hear a response within a timely manner, it is reasonable
to send your question a second time as a reminder, just in case we have
missed your original email (as you know, there is a VERY large volume of
email on the mailing list these days ;) In general, we strive to at
least set expectations for when we can review a question and provide
feedback but sometimes we forget to do this.
If this is not what you are asking, can you provide a specific example
for me? And then I can give you some suggestions on the process that is
best to follow.
Thanks,
Aliya
> -----Original Message-----
> From: Roberto Musso [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 22, 2008 2:42 AM
> To: Aliya Walji
> Subject: About IssueTracker
>
>
> Hi Aliya,
> I disturb you as I suppose that you are involved in the process on how
> submit the patch ("Aliya Walji" <[EMAIL PROTECTED]> ).
>
> My question is:
> 1. When a task is not just a patch , but require for eexamples an
> analysys
> or a UML diagram, what we have to do to submit the attachement at the
> attention of someone (not in the patch queues) so we are sure we get
an
> answer after a while?
>
> We have to resubmit the Issues to the Triage?
>
> Best
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
