... | ... | @@ -59,9 +59,11 @@ provided he/she has access to the data. |
|
|
|
|
|
### Update to existing packages
|
|
|
|
|
|
Usually, your experimental framework depends on several (bob) packages that you may have modified to suit your current needs. If this is the case and once you are done with your experiments, you basically have three choices to make sure that the functionalities you implemented will be available:
|
|
|
Usually, your experimental framework depends on several (bob) packages that you may want to modify to suit your current needs. As soon as you begin editing existing packages, a good practice would be to discuss the planned changes (typically in a merge request) you intend to make. This would allow a smooth integration of your code and ease the release of the modified / enhanced package as soon as you are done with it.
|
|
|
|
|
|
1. Merge all the changes you made and release a new version of the package(s).(this is the preferred way and the one you should aim for_
|
|
|
When modifying existing packages, you basically have three choices to make sure that the functionalities you implemented will be available:
|
|
|
|
|
|
1. Merge all the changes you made and release a new version of the package(s) - this is the preferred way and the one you should aim for.
|
|
|
2. Check out the specific branch / commit (in your ```buildout.cfg```)
|
|
|
3. Put the code directly in your paper package.
|
|
|
|
... | ... | |