Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Virgo/Committers/Process Advice
< Virgo | Committers
Revision as of 12:36, 7 December 2010 by Unnamed Poltroon (Talk) (→ssh keys; why and how to get them)
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)