On 10 November 2015 at 18:33, PGNet Dev
And, what's "improper" about the maintenance of packages currently in the devel & non-home repos?
Devel projects & all non-home repos are not tested. Our distributions are. Devel proejcts & all non-home repos do not have to follow our packaging policies and quality standards. Our distributions do Devel projects (and the majority of non-home repos) exist for a primary purpose of *developing* packages *before* their inclusion into Tumbleweed By definition that means Devel projects and non-home repos are going to be *BROKEN* at some point Because that is precisely the place where our developers have SO they can break stuff before it hits one of our distributions In fact, if those projects are NOT breaking from time to time, then I argue that the maintainers are doing something wrong Yes, I know people like to see those projects as shortcuts to the latest version of software Yes, I know people are going to use the packages in those projects regardless of what I say Yes, I know there are some Projects which do a very good job of very carefully being 'Stable' sources of addition packages for our users But there is no way in heck I'm going to loose sleep about the fact that Leap 42.1 doesn't have those repos enabled yet when the answer is simple If people want those packages in the release of openSUSE Leap 42.1, they should have submitted them to the release of openSUSE Leap 42.1 And the same will be true for 42.2..if people want those packages in our next release next year, get them in Tumbleweed now, and make sure they get into Leap 42.2 next year. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org