[jira] [Created] (IGNITE-13526) Ignite Docs: document contribution and release processes

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (IGNITE-13526) Ignite Docs: document contribution and release processes

Anton Vinogradov (Jira)
Denis A. Magda created IGNITE-13526:
---------------------------------------

             Summary: Ignite Docs: document contribution and release processes
                 Key: IGNITE-13526
                 URL: https://issues.apache.org/jira/browse/IGNITE-13526
             Project: Ignite
          Issue Type: Bug
          Components: documentation
            Reporter: Denis A. Magda
            Assignee: Denis A. Magda
             Fix For: 2.10


We need to document the contribution, maintenance, and release processes. Some pointers for the beginning:

* https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document
* https://github.com/apache/ignite/blob/IGNITE-7595/docs/README.adoc
* How to build and test locally before pushing changes (using the ignite repository that stores the docs' sources)
* How to transform the docs into the HTML and deploy on the website:
* How to add a page to the navigation menu
* How to set up redirects if page's URL is changed (seems this has to be done on the website end)


Explain how to create callouts:

{noformat}
[CAUTION]
====
[discrete]
=== Embedded Mode Deprecation
Embedded mode implies starting Ignite server nodes within Spark executors which can cause unexpected rebalancing or even data loss. Therefore this mode is currently deprecated and will be eventually discontinued. Consider starting a separate Ignite cluster and using standalone mode to avoid data consistency and performance issues.
====
{noformat}

{noformat}
[NOTE]
====
[discrete]
=== Embedded Mode Deprecation
Embedded mode implies starting Ignite server nodes within Spark executors which can cause unexpected rebalancing or even data loss. Therefore this mode is currently deprecated and will be eventually discontinued. Consider starting a separate Ignite cluster and using standalone mode to avoid data consistency and performance issues.
====
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)