Hey Ludwig, On 07.02.19 14:19, Ludwig Nussel wrote:
Saray Cabrera Padron schrieb:
[...] We have written down a little bit what we did so far for you: https://gist.github.com/saraycp/ddda1cc4b622149926287b0cadede46b
Rest assured we are working on making this a complete OBS feature. Please test as much as you can now and do not hesitate tocontact our
I'm not sure what is expected from us here. How are we supposed to do that exactly? To me it looks like the state is too early for us to do anything practical.
Sure, like we said, this is the first shot at it. It's in no way meant to be for productive use. However maybe you can take it as far as you can take it and tell us what you think? What you like and what you don't like, opportunities you see? That is what we are looking for, so when we do more iterations of this, with the gained insight from you.
The staging projects you have there are empty and do not build.
Because nobody staged anything yet :-)
None of us is in the required group to interact with the system.
Sorry, we forgot to mention this in the announcement. You are now, so are Coolo and Anja. Just drop me an email if you need more people in it.
The test packages in your test project are unknown to me
Does this matter for the functionality that is there? It's "sample" data so you can stage/unstage & ignore/unignore a few requests, look at the results and play with the creation.
If you want feedback about the real tricks and corner cases we need the packages we know in a familiar setup. We don't want feedback about the things that are not there. We want feedback about the things that are there.
According to your documentation operations on that new staging workflow require manual API calls anyways. TBH I'm not really eager to learn more OBS API calls You don't have to, you can copy and paste. And maybe if you don't have the time to do it, someone else can? Especially your people who will consume the API and not the UI.
It's okay if this is not for you. We're just asking for feedback. Up to you what you want to do about this.
Give me the user interface and tools I need instead please :-)
Like we wrote, this is what we have now. osc command and user interfaces are planed for iterations in the future.
The other alternative I see is that you will be given access to an existing product's staging (I can offer Leap) and you'll quickly figure out yourself where the trouble is.
We have a pretty good understanding about where the trouble is, we talked about this already a couple of times and we will continue to talk to you about this, we will continue to involve your Architect into the development of concepts and code. But additionally to that we want your feedback on the steps we take. You do this with your own products all the time don't you? Alpha releases, beta programs, customer approval phases, yadda yadda yadda :-) Henne -- Hendrik Vogelsang, Open Build Service Team SUSE LINUX GmbH, GF: Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-releaseteam+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-releaseteam+owner@opensuse.org