[opensuse-buildservice] openSUSE Build Service 1.0 Release Candidate available
We just released the Build Service 1.0 release candidate. The final release is expected in two weeks. Most important about this release are the improvements in source handling. Submissions to foreign projects are possible now. That does mean that after two years of development, direct work on openSUSE distribution becomes possible, with bugzilla in between ! You see, we need sometimes a bit longer, but we keep our promises :) The Build Service at http://build.opensuse.org is already running it, so it can be already used for submissions. You just need the current osc from openSUSE:Tools project. When editing a package in openSUSE:Factory, you work usually on a branch of the maintainers project. In this way everybody can work close together with the official maintainers. These mechanism are usable via the osc command line client already. But the functionality is provided by the server, so I hope we can easily make the same functionality accessible in the other clients soon. We have a wiki page describing the way how to use this: http://en.opensuse.org/Build_Service/Collaboration We expect still some rough edges in the functionality, but only practical usage will show them. A 1.1 has been added to the roadmap, which can improve these use cases: http://en.opensuse.org/Build_Service/Roadmap Please keep in mind that Factory is frozen atm to get 11.0 out of the door. So submissions will not get check in in the next week. But they can get already prepared :) have fun Your Build Service Team -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 11 June 2008 13:19:51 Adrian Schröter wrote:
We just released the Build Service 1.0 release candidate. The final release is expected in two weeks.
Most important about this release are the improvements in source handling. Submissions to foreign projects are possible now. That does mean that after two years of development, direct work on openSUSE distribution becomes possible, with bugzilla in between ! You see, we need sometimes a bit
Urgs, that should mean _WITHOUT_ bugzilla of course :) -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
2008/6/11 Adrian Schröter
We have a wiki page describing the way how to use this:
http://en.opensuse.org/Build_Service/Collaboration
We expect still some rough edges in the functionality, but only practical usage will show them. A 1.1 has been added to the roadmap, which can improve these use cases: Is the "The maintainer of a project (like openSUSE:Factory) *is supposed* to check for contributions (i.e. for submit requests)" going to be this way in the future? Right now we already have submitreqs ignored. I think the older one is number 54, from 2008-05-15.
I myself don't do it too much since I don't expect people looking my home repo where 90% of packages are 80's game remakes. But if someday someone sends me a patch, it could easily pass two or three months until I see it. I would like to be informed someway about submitreqs sent to me.
On Wed, 2008-06-11 at 13:19 +0200, Adrian Schröter wrote:
We just released the Build Service 1.0 release candidate. The final release is expected in two weeks.
Most important about this release are the improvements in source handling. Submissions to foreign projects are possible now. That does mean that after two years of development, direct work on openSUSE distribution becomes possible, with bugzilla in between ! You see, we need sometimes a bit longer, but we keep our promises :)
The Build Service at http://build.opensuse.org is already running it, so it can be already used for submissions. You just need the current osc from openSUSE:Tools project.
I notice that you can't do submitreq without branching first. So the following won't work: osc submitreq create -m 'This will fail' GNOME:Community banshee \ home:maw Feature or, uh, missing feature? Also, submitreq is rather poorly named. :( "mergereq" might make more sense. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 13 June 2008 03:27:12 Michael Wolf wrote:
On Wed, 2008-06-11 at 13:19 +0200, Adrian Schröter wrote:
We just released the Build Service 1.0 release candidate. The final release is expected in two weeks.
Most important about this release are the improvements in source handling. Submissions to foreign projects are possible now. That does mean that after two years of development, direct work on openSUSE distribution becomes possible, with bugzilla in between ! You see, we need sometimes a bit longer, but we keep our promises :)
The Build Service at http://build.opensuse.org is already running it, so it can be already used for submissions. You just need the current osc from openSUSE:Tools project.
I notice that you can't do submitreq without branching first. So the following won't work:
osc submitreq create -m 'This will fail' GNOME:Community banshee \ home:maw
Feature or, uh, missing feature?
banshee does not exist yet in home:maw ? We have an open bugreport for this situation :/
Also, submitreq is rather poorly named. :( "mergereq" might make more sense.
Hm, we had this in this proposal, but agreed to switch to submit. IIRC because also new code submissions should work, which is not a merge technically. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter escribió:
We have an open bugreport for this situation :/
the bug : https://bugzilla.novell.com/show_bug.cgi?id=398758 ;-) -- "Progress is possible only if we train ourselves to think about programs without thinking of them as pieces of executable code.” - Edsger W. Dijkstra Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
On Fri, 2008-06-13 at 10:04 +0200, Adrian Schröter wrote: [..]
I notice that you can't do submitreq without branching first. So the following won't work:
osc submitreq create -m 'This will fail' GNOME:Community banshee \ home:maw
Feature or, uh, missing feature?
banshee does not exist yet in home:maw ?
We have an open bugreport for this situation :/
Well, it's too bad it doesn't work yet, but I'm glad that it's already a known issue. :) Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, Jun 12, 2008 at 08:27:12PM -0500, Michael Wolf wrote:
On Wed, 2008-06-11 at 13:19 +0200, Adrian Schröter wrote:
We just released the Build Service 1.0 release candidate. The final release is expected in two weeks.
Most important about this release are the improvements in source handling. Submissions to foreign projects are possible now. That does mean that after two years of development, direct work on openSUSE distribution becomes possible, with bugzilla in between ! You see, we need sometimes a bit longer, but we keep our promises :)
The Build Service at http://build.opensuse.org is already running it, so it can be already used for submissions. You just need the current osc from openSUSE:Tools project.
I notice that you can't do submitreq without branching first. So the following won't work:
osc submitreq create -m 'This will fail' GNOME:Community banshee \ home:maw
Feature or, uh, missing feature?
It would work if the target package already exists at the place where you want to submit it. It is a bug, as others already wrote. Another open bug is that it is not possible to delete a submit request, once it has been issued. (Only the owner of the destination project can do that.)
Also, submitreq is rather poorly named. :( "mergereq" might make more sense.
It may seem like (intended to be a) a merge at first, but technically it is not a merge, but a copy. It will overwrite the target package, _not_ apply a diff with the differences. (Especially when you want to submit the package to some place where it doesn't exist yet ;-) Maybe this should be made more clear on the collaboration page. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Le vendredi 13 juin 2008, à 10:24 +0200, Peter Poeml a écrit :
On Thu, Jun 12, 2008 at 08:27:12PM -0500, Michael Wolf wrote:
Also, submitreq is rather poorly named. :( "mergereq" might make more sense.
It may seem like (intended to be a) a merge at first, but technically it is not a merge, but a copy. It will overwrite the target package, _not_ apply a diff with the differences.
(Especially when you want to submit the package to some place where it doesn't exist yet ;-)
Maybe this should be made more clear on the collaboration page.
Sorry for the late feedback on this -- it was not clear to me how exactly this would work before I read the collaboration page :/ I'm confused by something else: it looks to me like "submitreq" is, well, to submit a request, and it sounds weird to use this to also list/accept/decline/show requests. I know you've discussed the name of the command for quite some time and the name was not easy to choose, but I wonder about the reasons for not choosing something like "request" or "collab". Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, Jun 13, 2008 at 10:55:48AM +0200, Vincent Untz wrote:
Sorry for the late feedback on this -- it was not clear to me how exactly this would work before I read the collaboration page :/
But if it became clear to you after you read it? Well, then I'm fine. That's why 'osc help submitreq' gives the link :-)
I'm confused by something else: it looks to me like "submitreq" is, well, to submit a request, and it sounds weird to use this to also list/accept/decline/show requests. I know you've discussed the name of the command for quite some time and the name was not easy to choose, but I wonder about the reasons for not choosing something like "request" or "collab".
Vincent
Feedback is always welcome, also late ;-) You could see it as this: "submitreq" is a subcommand to handle submit requests. It means "request a submission", rather than "submit a request". Maybe the command could be called "submission" instead. "request" was already taken as subcommand. There are more request types planned to be implemented in the future (no concrete plans, but ideas). Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Le vendredi 13 juin 2008, à 11:04 +0200, Peter Poeml a écrit :
On Fri, Jun 13, 2008 at 10:55:48AM +0200, Vincent Untz wrote:
Sorry for the late feedback on this -- it was not clear to me how exactly this would work before I read the collaboration page :/
But if it became clear to you after you read it? Well, then I'm fine.
Yeah, the page helps a lot :-) [...]
You could see it as this: "submitreq" is a subcommand to handle submit requests.
Maybe it's my non-native english brain, but I really first think about the action of submitting a request and not about handling submitted requests...
It means "request a submission", rather than "submit a request". Maybe the command could be called "submission" instead.
"submission" sounds better to me (but it's a bit longer to type...) Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 13 June 2008 11:25:40 Vincent Untz wrote:
Le vendredi 13 juin 2008, à 11:04 +0200, Peter Poeml a écrit : ...
You could see it as this: "submitreq" is a subcommand to handle submit requests.
Maybe it's my non-native english brain, but I really first think about the action of submitting a request and not about handling submitted requests...
It means "request a submission", rather than "submit a request". Maybe the command could be called "submission" instead.
"submission" sounds better to me (but it's a bit longer to type...)
What about "submit" ? bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Le vendredi 13 juin 2008, à 11:51 +0200, Adrian Schröter a écrit :
On Friday 13 June 2008 11:25:40 Vincent Untz wrote:
Le vendredi 13 juin 2008, à 11:04 +0200, Peter Poeml a écrit : ...
You could see it as this: "submitreq" is a subcommand to handle submit requests.
Maybe it's my non-native english brain, but I really first think about the action of submitting a request and not about handling submitted requests...
It means "request a submission", rather than "submit a request". Maybe the command could be called "submission" instead.
"submission" sounds better to me (but it's a bit longer to type...)
What about "submit" ?
Don't know, "osc submit accept" sounds weird to me. It's better than submitreq in some way, but I'd say it mostly has the same issues and has an additional one: "submit" sounds generic and so the user might think "do I want to commit or to submit?" :/ Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 13 June 2008 12:25:30 Vincent Untz wrote:
Le vendredi 13 juin 2008, à 11:51 +0200, Adrian Schröter a écrit :
On Friday 13 June 2008 11:25:40 Vincent Untz wrote:
Le vendredi 13 juin 2008, à 11:04 +0200, Peter Poeml a écrit :
It means "request a submission", rather than "submit a request". Maybe the command could be called "submission" instead.
"submission" sounds better to me (but it's a bit longer to type...)
What about "submit" ?
Don't know, "osc submit accept" sounds weird to me. It's better than submitreq in some way, but I'd say it mostly has the same issues and has an additional one: "submit" sounds generic and so the user might think "do I want to commit or to submit?" :/
What about following the "osc NOUN VERB" pattern sort of used by osc meta? I suggest using "requests" rather than "request" as it is less easily confused with the verb osc requests submit ... osc requests list ... osc requests show ... osc requests decline ... osc requests accept ... Alternatively keep the verbs as is and use "submission" instead of "submitreq" which does betray its origins as a pure submit. Will --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Will Stephenson napsal(a):
On Friday 13 June 2008 12:25:30 Vincent Untz wrote:
Don't know, "osc submit accept" sounds weird to me. It's better than submitreq in some way, but I'd say it mostly has the same issues and has an additional one: "submit" sounds generic and so the user might think "do I want to commit or to submit?" :/
What about following the "osc NOUN VERB" pattern sort of used by osc meta? I suggest using "requests" rather than "request" as it is less easily confused with the verb osc requests submit ... osc requests list ... osc requests show ... osc requests decline ... osc requests accept ...
I like this. Maybe add 'req' and 'request' as aliases to 'requests'. A minor problem is that there's a 'req' command already, but that's used for debugging purposes mostly, so it should be ok to rename it to 'httpreq' or something like that. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 13 June 2008 15:45:20 Michal Marek wrote:
Will Stephenson napsal(a):
On Friday 13 June 2008 12:25:30 Vincent Untz wrote:
Don't know, "osc submit accept" sounds weird to me. It's better than submitreq in some way, but I'd say it mostly has the same issues and has an additional one: "submit" sounds generic and so the user might think "do I want to commit or to submit?" :/
What about following the "osc NOUN VERB" pattern sort of used by osc meta? I suggest using "requests" rather than "request" as it is less easily confused with the verb osc requests submit ... osc requests list ... osc requests show ... osc requests decline ... osc requests accept ...
I like this. Maybe add 'req' and 'request' as aliases to 'requests'. A minor problem is that there's a 'req' command already, but that's used for debugging purposes mostly, so it should be ok to rename it to 'httpreq' or something like that.
yep, sound good to me as well. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, 2008-06-13 at 10:24 +0200, Peter Poeml wrote: [...]
Also, submitreq is rather poorly named. :( "mergereq" might make more sense.
It may seem like (intended to be a) a merge at first, but technically it is not a merge, but a copy. It will overwrite the target package, _not_ apply a diff with the differences.
(Especially when you want to submit the package to some place where it doesn't exist yet ;-)
Maybe this should be made more clear on the collaboration page.
Understood, but is the distinction interesting to users, or just you the implementors? Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, Jun 13, 2008 at 08:26:03AM -0500, Michael Wolf wrote:
On Fri, 2008-06-13 at 10:24 +0200, Peter Poeml wrote:
[...]
Also, submitreq is rather poorly named. :( "mergereq" might make more sense.
It may seem like (intended to be a) a merge at first, but technically it is not a merge, but a copy. It will overwrite the target package, _not_ apply a diff with the differences.
(Especially when you want to submit the package to some place where it doesn't exist yet ;-)
Maybe this should be made more clear on the collaboration page.
Understood, but is the distinction interesting to users, or just you the implementors?
Yes. Interesting to users. A merge would not overwrite the target, if the "diff" doesn't "apply" anymore. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
participants (8)
-
Adrian Schröter -
Christian Morales Vega -
Cristian Rodríguez -
Michael Wolf -
Michal Marek -
Peter Poeml -
Vincent Untz -
Will Stephenson