Am 21.03.2016 um 13:43 schrieb Yamaban:
Otherwise, I'd like to call out to all interrested parties, for proposals of:
- of upgrades in package versions for 42.2
- added packages to 42.2 (new, replacement for, ...)
- removal of packages from 42.2, (EOL, replaced by, ...)
Now since I finally had the time to look at packages which are interesting to me and my usecase.
Can we as a maintainer group agree, that we do not want to discuss every single update request on the list which the above seems to imply?
We have OBS and AFAIK it handles the case correctly when a package update is submitted from a non-maintainer that it'll automatically insert a review request to the actual maintainer. If that is the case I propose at least to handle "simple" upgrade and insertion requests like this.
What is "simple" in the end is not always easy to decide and if in doubt this should be discussed between the requester and the maintainer or if it even has a bigger impact and no agreement we should bring it to this list probably.
Can we agree on this simplification or is this already written in some process I missed?
We can also define something else if necessary but using existing tools might help to improve efficiency.
Another thing I'm wondering about is how to easily monitor updates to 42.2 which are either "forks" or pulled in from Factory (compared to updates automatically pulled in from SLES12 and 42.1 updates).
Because I think it makes a lot of sense to have as many eyes as possible on those updates to assess if the upgrade path from 42.1 to 42.2 stays feasible as we try to position Leap 42 as some kind of LTS (similar to SLES service packs).
Currently I see https://build.opensuse.org/package/view_file/openSUSE:Leap:42.2/00Meta/looku... as a snapshot which is not too easy to work with.
So question to Ludwig who does a great job with the "New Tumbleweed snapshot XXX released": Would it be possible and feasible to have something similar for the ongoing 42.2 work?