Tasks #1437
Provide testing repository
| Status: | Resolved | Start date: | 02/25/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | M. Goetting | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
Apart from the main repository we have now, I would like to propose a testing repository, too, where we deploy unstable / testing packages. The need was raised in AMARSi, where some of our packages will depend on packages of some partner's testing packages/repository. But I even think, this could make sense for our core packages, maybe even all our non-release (trunk) packages. The positive effect would be that users would have to actively decide on using testing packages and would now that they have to be prepared for changes, API breaks, and stuff.
This would probably require slightly adapting our CI upload policies, e. g. to push packages touplaod/main/${ubuntu_release}andupload/testing/${ubuntu_release}
(currently just upload/${ubuntu_release})
History
#1 Updated by J. Wienke about 11 years ago
Michael and I have talked about this some time ago and basically agreed on this. So it should just be done.
#2 Updated by Anonymous about 11 years ago
- Status changed from Feedback to New
Very well, then!
@Michael: Could you have a look at this and propose an CI uploading policy, that we then can batch-update on Jenkins with Jan's tools?
#3 Updated by J. Moringen about 7 years ago
- Status changed from New to Resolved
We do this already, I think. Doesn't matter anymore if we don't.