cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: Cordova Issue Workflow
Date Tue, 22 Oct 2013 14:07:23 GMT
Great feedback Josh!

Are you looking for answers to these shortcomings? If you're just looking
for a +1 please improve the wiki, then... +1!


On Mon, Oct 21, 2013 at 8:55 PM, Josh Soref <jsoref@blackberry.com> wrote:

> Google <https://www.google.ca/?q=cordova+issue+workflow> tells me that
> there's a ContributorWorkflow:
> http://wiki.apache.org/cordova/ContributorWorkflow
>
> But:
> 1. Creating/finding an issue is buried in text in the middle of the "About
> Commit Messages" -- that can't possibly be where one creates or finds a
> bug in anyone's actual workflow.
> 2. It doesn't say how/when issues are updated.
> 3. It doesn't say if one should try to have an issue assigned if they're
> working on it.
> 4. "Review Board is a tool for committers to review each others' changes.
> As a contributor generally you won't use Review Board - the pull request
> should be sufficient." -- There's no link to review board.
> 5. It doesn't explain the Version fields (found/fixed) -- neither who
> should fill them out/according to whatŠ
> 6. It doesn't explain how an issue should be resolved / what steps should
> be taken. There seems to be a difference between something being "Fixed"
> and something being "Resolved".
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential
> information, privileged material (including material protected by the
> solicitor-client or other applicable privileges), or constitute non-public
> information. Any use of this information by anyone other than the intended
> recipient is prohibited. If you have received this transmission in error,
> please immediately reply to the sender and delete this information from
> your system. Use, dissemination, distribution, or reproduction of this
> transmission by unintended recipients is not authorized and may be unlawful.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message