Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Platform-releng-faq"

(David williams.us.ibm.com moved page Platform-releng-faq to Platform-releng-faq-obsolete: Most of the data in this faq is obsolete, but may still contain some interesting tid-bits.)
 
m (removed extra ']')
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
#REDIRECT [[Platform-releng-faq-obsolete]]
+
{{warning| The document that used to be here has been moved to [[Platform-releng-faq-obsolete]] because the majority of [[Platform-releng-faq-obsolete]] was no longer accurate. There might still be some items there that are still true or interesting for some people, and, ideally, someone could, someday, go through each item carefully and decide if there is any merit to moving the item "up" to this document. But in the meantime, it was thought best to "start over".}}
 +
 
 +
== Where are the basics of the Platform build documented? ==
 +
 
 +
In [[Platform-releng/Platform_Build| Platform Build]].
 +
 
 +
== Does that Platform Build document describe the so-called Production Build? ==
 +
 
 +
No, not exactly. It forms the heart of the production build, but there are other things done in the production build. Those are described in [[Platform-releng/Platform_Build_Automated| Platform Build Automated]]. So in general, anyone wanting to learn or reproduce our build should first read [[Platform-releng/Platform_Build| Platform Build]] and then read [[Platform-releng/Platform_Build_Automated| Platform Build Automated]].
 +
 
 +
== What other tasks does Platform Releng do? ==
 +
 
 +
Other tasks are described in several other documents, each has various degrees of accuracy or being up do date:
 +
 
 +
: [[Platform-releng/How_to_do_miscellaneous_releng_tasks| miscellaneous releng tasks]]
 +
: [[Platform-releng/Checklist| releng checklists]]
 +
: [[Platform-releng/Updating_Branding| updating branding]]
 +
 
 +
== Are there documents that Platform committers should read or be aware of? ==
 +
 
 +
The following are good, though some sections may need to be brought up to date.
 +
 
 +
: [[Eclipse/Rhythm| the Eclipse Projects rhythm]]
 +
: [[Platform-releng/Incrementing_Version_Numbers| incrementing version numbers]]
 +
: [[Platform-releng/Automated_Testing| automated (production) testing]]
 +
: [[Performance/Automated_Tests| performance testing]]
 +
 
 +
[Feel free to add more items to this document, when questions are frequently asked.]
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
 
 +
[[Category:FAQ]]
 +
[[Category:Releng]]
 +
[[Category:Eclipse_Platform_Releng| ]]

Revision as of 09:40, 15 August 2016

Warning2.png
The document that used to be here has been moved to Platform-releng-faq-obsolete because the majority of Platform-releng-faq-obsolete was no longer accurate. There might still be some items there that are still true or interesting for some people, and, ideally, someone could, someday, go through each item carefully and decide if there is any merit to moving the item "up" to this document. But in the meantime, it was thought best to "start over".


Where are the basics of the Platform build documented?

In Platform Build.

Does that Platform Build document describe the so-called Production Build?

No, not exactly. It forms the heart of the production build, but there are other things done in the production build. Those are described in Platform Build Automated. So in general, anyone wanting to learn or reproduce our build should first read Platform Build and then read Platform Build Automated.

What other tasks does Platform Releng do?

Other tasks are described in several other documents, each has various degrees of accuracy or being up do date:

miscellaneous releng tasks
releng checklists
updating branding

Are there documents that Platform committers should read or be aware of?

The following are good, though some sections may need to be brought up to date.

the Eclipse Projects rhythm
incrementing version numbers
automated (production) testing
performance testing

[Feel free to add more items to this document, when questions are frequently asked.]

Back to the top