Forgot your password?
typodupeerror
Linux Business Operating Systems SuSE Linux

OpenSUSE Team Reworking Dev Model, Delays 12.2 Release 38

Posted by timothy
from the when-big-turns-make-sense dept.
LinuxScribe writes "The upcoming 12.2 RC1 release of openSUSE has been delayed, and the final 12.2 release 'won't see the light of day on July 11th,' as developers within the openSUSE community struggles to fix their release efforts, Community Manager Jos Poortvliet said today." Says the article: "Among [openSUSE Release Manager Stephan] Kulow's suggestions? Dumping the current release cycle schedule for openSUSE and moving to an annual or even unscheduled release system."
This discussion has been archived. No new comments can be posted.

OpenSUSE Team Reworking Dev Model, Delays 12.2 Release

Comments Filter:
  • by ThePhilips (752041) on Thursday June 14, 2012 @09:18AM (#40321599) Homepage Journal

    Linux folks don't have nearly the trouble as they're a tier 1 platform for most software these days.

    On the positive side, if you know Linux, you have better chances of finding why the piece of software refuses to compile/link.

    I'm no distro maintainer, but I do a share of platform porting. In my experience it is actually reliance on GCC (and prehistoric crap inside /usr/include/) which is more of a problem. Only after experiencing all that fun trying to compile open source software using non-GCC compilers (aCC, SunStudio, xlc), I have fully realized what kind of hurdle CLang developers and users have ahead of them.

  • by Anonymous Coward on Thursday June 14, 2012 @11:49AM (#40323373)

    Part of the problem with Linux in general, and Suse in particular, is that when you do file a bug report the response is "work on it yourself." I filed bug report once After carefully documenting how to cause a serious problem and filing a bug report detailing the steps to reproduce it. I'm not a developer and didn't want to become one. However, I am a reasonably knowledgeable user. Out of courtesy I spent many hours tracking down the exact sequence of events which would cause the issue, corruption of a configuration file. (No, I wasn't messing with the file myself. I was using standard tools in the distribution to configure remote access through VNC.) I figured I'd done a good thing and someone would pick up the information I had submitted and fix the error. Instead I got a response asking me to track down the source code and recommend a patch. When I explained that I was not in a position to do that I was told "Well, that's the way the community works. If you don't have time to work on the problem we don't have time to help you." I was stunned.

Serving coffee on aircraft causes turbulence.

Working...