User Tools
developingpld
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
developingpld [2013-12-24 20:40] glen [Working on packages] |
developingpld [2014-05-13 18:34] (current) glen Links to acinfo changed to ac |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| * PLD Ra/1.0 (released some time ago) | * PLD Ra/1.0 (released some time ago) | ||
| - | * [[:AcInfo|PLD Ac/2.0]] (stable) | + | * [[ac|PLD Ac/2.0]] (stable) |
| - | * [[:ThInfo|PLD Th/3.0]] (in development) | + | * [[th|PLD Th/3.0]] (in development) |
| Each line has a person in charge of it, called the Release Manager. RMs spend time maintaining parts of PLD's infrastructure, making decisions if other developers can't agree on something by themselves and taking care of the content of our FTP server. | Each line has a person in charge of it, called the Release Manager. RMs spend time maintaining parts of PLD's infrastructure, making decisions if other developers can't agree on something by themselves and taking care of the content of our FTP server. | ||
| Line 102: | Line 102: | ||
| ==== Publishing your changes ==== | ==== Publishing your changes ==== | ||
| - | As a wannabe developer you most likely won't have read/write access to the CVS repository so you'll have to find someone to check your changes in and add them to the repository. The best way to do it is to send a //unified diff// of your changes against the original files (or the whole files in case you are adding any) in a mail message along with a brief description of what you did to the ''pld-devel-en'' (or ''pl'') mailing list. | ||
| - | Once one of the other developers has time to review your changes, you will be notified of any errors that need to be fixed and eventually your files will get commited. | + | As a wannabe developer you most likely won't have read/write access to the GIT repository so you'll have to find someone to check your changes in and add them to the repository. The best way to do it is to send a //unified diff// of your changes against the original files (or the whole files in case you are adding any) in a mail message along with a brief description of what you did to the ''pld-devel-en'' (or ''pl'') mailing list. |
| - | Once you provide enough valuable changes, other developers might decide to give you full access to our repositories. This process is always initiated by someone who already has read/write access, asking for access on your own will not do you any good. | + | It's also acceptable to make your changes in your git repository, perhaps published in [[https://github.com|github]] and let somebody to pull your changes to pld repository. |
| - | When that happens, you will be able to do regular CVS commits. Remember to check the files you are committing before sending them to the repository. Make sure you also provide a meaningful commitlog. All logs have to be in the following format: | + | Once existing developer, who has time to review your changes, you will be notified of any errors that need to be fixed and eventually your files will get committed or pushed. |
| + | Once you provide enough valuable changes, other developers might decide to give you full access to our repositories. This process is always initiated by someone who already has read/write access, asking for access on your own will not do you any good. | ||
| + | When that happens, you will be able to do GIT commits and push them to PLD servers yourself. Remember to check the files you are committing before sending them to the repository. Make sure you also provide a meaningful commitlog. All logs have to be in the following format: | ||
| <file>- first change | <file>- first change | ||
developingpld.1387914043.txt.gz · Last modified: 2013-12-24 20:40 by glen
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
