'How to Contribute' wiki page updated.

[Anton Vinogradov-2]

Igniters,

https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute page
updated.

Changes:
1) Jira process and Git process becomes part of How to Contribute
<https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute>.
2) Added 'Ticket Branch' case (only for committers).
3) Fixed minor issues.

It will be nice if someone check correctness.

[dsetrakyan]

Thanks, Anton!

I think the whole process looks too big right now. Perhaps we can make the
following changes:

   - Remove "Development Process" section (not sure if it applies to us).
   - Remove "Git Workflow" section as it is described already in "Workflow"
   section.
   - Remove "Git Branches" section
   - "Release Process" section should be a numbered list describing steps
   (including QA branch) necessary to create a release.
   - For the ticket branch section, I don't think it is clear how to submit
   a branch for review or how to apply changes on master. Would be nice if you
   could clarify.
   - I would add Continuous Integration section with URL to TeamCity. It
   should also state that merges to master should only happen after the whole
   TC suite passes.

Raul, it would be nice if you could also take a look and provide comments.

Thanks,
D.

On Mon, Oct 5, 2015 at 7:36 AM, Anton Vinogradov <[hidden email]> wrote:

> Igniters,
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute page
> updated.
>
> Changes:
> 1) Jira process and Git process becomes part of How to Contribute
> <https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute>.
> 2) Added 'Ticket Branch' case (only for committers).
> 3) Fixed minor issues.
>
> It will be nice if someone check correctness.
>

[Anton Vinogradov]

Dmitriy,

I've fixed page according to your request except:

>    - "Release Process" section should be a numbered list describing steps
>    (including QA branch) necessary to create a release.

As far as I understans there is no QA's at Ignite community. GridGain QAs
can provide some help, but it's not a part of Ignite release process.
Another steps Prepare->Vote->Release are declared at Apache site and they
are the same for all projects.

   - I would add Continuous Integration section with URL to TeamCity. It
>    should also state that merges to master should only happen after the
> whole
>    TC suite passes.

Each case at workflow ends with phrase similar to:
"Run TC tests.Once tests are passed, the pull request can be reviewed and
merged by a committer."
Is it enough?

On Tue, Oct 6, 2015 at 8:10 AM, Dmitriy Setrakyan <[hidden email]>
wrote:

> Thanks, Anton!
>
> I think the whole process looks too big right now. Perhaps we can make the
> following changes:
>
>    - Remove "Development Process" section (not sure if it applies to us).
>    - Remove "Git Workflow" section as it is described already in "Workflow"
>    section.
>    - Remove "Git Branches" section
>    - "Release Process" section should be a numbered list describing steps
>    (including QA branch) necessary to create a release.
>    - For the ticket branch section, I don't think it is clear how to submit
>    a branch for review or how to apply changes on master. Would be nice if
> you
>    could clarify.
>    - I would add Continuous Integration section with URL to TeamCity. It
>    should also state that merges to master should only happen after the
> whole
>    TC suite passes.
>
> Raul, it would be nice if you could also take a look and provide comments.
>
> Thanks,
> D.
>
> On Mon, Oct 5, 2015 at 7:36 AM, Anton Vinogradov <[hidden email]> wrote:
>
> > Igniters,
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> page
> > updated.
> >
> > Changes:
> > 1) Jira process and Git process becomes part of How to Contribute
> > <https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute>.
> > 2) Added 'Ticket Branch' case (only for committers).
> > 3) Fixed minor issues.
> >
> > It will be nice if someone check correctness.
> >
>