On Fri, Jul 15, 2016 at 11:39 AM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Content-ID: <alpine.LSU.2.20.1607151737371.5759@Grypbagne.inyvabe>
On Wednesday, 2016-07-06 at 18:38 -0400, Greg Freemyer wrote:
On Wed, Jul 6, 2016 at 5:17 PM, Andrei Borzenkov <> wrote:
On Wed, Jul 6, 2016 at 11:47 PM, Greg Freemyer <> wrote:
5 years ago the openSUSE devs would ask for bugzilla entries. Now they strongly prefer SRs.
Update to released version still requires bugzilla. For Factory you indeed can just submit SR to package development repo, and it at some point ends up in Factory.
Yes, I was definitely talking about efforts to get changes into factory.
I read your post several times, thanks. It is in my ToDo list to try these things. But I do not use factory aka tumbleweed. I have a test install under vmware, though, but what I do there is quite limited to some tests.
I don't use factory either, but it is "the way" to get routine package changes into the distro. For the rsnapshot doc change I did: - I SR'ed the change to the devel package, - it got forward-SR'ed to factory, - from factory it was forward-SR'ed to Leap 42.2 (for release in the fall) Ignoring SUSE as a route for changes, the above is the only approved method for getting routine updates in Leap 42.2 The only way to get a change directly in a package and bypass factory is to write a bugzilla against Leap 42.1. All maintenance updates for Leap 42.1 are also forwarded to Leap 42.2. fyi: I'm a rsnapshot maintainer, so I did the the 2 SR forwards. In general, each package has one or more maintainers. They should handle the SR forwarding. You just send the SR to the devel package. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org