Jump to: navigation, search

Difference between revisions of "Virgo/Committers/Process Advice"

(First cut)
 
(ssh keys; why and how to get them)
Line 7: Line 7:
 
== ssh keys; why and how to get them ==
 
== ssh keys; why and how to get them ==
  
* git.eclipse.org
+
Set up ssh keys so that you are not prompted for a password at many and/or inconvenient points.
* build.eclipse.org
+
 
* (other?)
+
* git.eclipse.org - instructions [http://wiki.eclipse.org/Git#Setting_up_ssh_keys here]
 +
* build.eclipse.org - same procedure as for git.eclipse.org
 +
 
 +
To request a full shell, either raise a [https://bugs.eclipse.org/bugs/show_bug.cgi?id=312034#c3 bugzilla] or email webmaster@eclipse.org. Probably best to email and ask for a full shell on both the above servers.
  
 
== how to fix a bug ==
 
== how to fix a bug ==

Revision as of 11:36, 7 December 2010


Development advice for committers

These sections are incomplete. Please either supply the required details or request more information if you require it.

ssh keys; why and how to get them

Set up ssh keys so that you are not prompted for a password at many and/or inconvenient points.

  • git.eclipse.org - instructions here
  • build.eclipse.org - same procedure as for git.eclipse.org

To request a full shell, either raise a bugzilla or email webmaster@eclipse.org. Probably best to email and ask for a full shell on both the above servers.

how to fix a bug

All our enhancements and bugs (in fact, every change that happens to the product or the code base) start life with a bugzilla. We generically refer to them all as bugs. Bugzilla entries should record any information associated with the change.

To make it easier to share the work it is helpful to follow some simple guidelines:

  • starting work on a bug
  • giving up on a bug
  • closing a bug

what is a ripple and when to do one

(don't)

creating a release (milestone or higher)

(tbd)