The Testing Core Team held a meeting on Monday, December 12, 2011 at 18:00 UTC
on Channel #opensuse-testing on the Freenode IRC Network
(irc://irc.freenode.net/opensuse-testing).
For most of the meeting, we discussed the openSUSE 12.1 release cycle. The full
transcript of the meeting is found at http://tinyurl.com/cnog4af, but we agreed
that too many bugs make it into the released version. Our discussion centered
around two main points.
1. Many people do not start testing until RC1 or RC2 are released; however, by
then there is too little time for the bugs to be fixed. For 12.1, this problem
was worse due to the late release of some of the milestones, which made the RC
cycle shorter than it usually will be.
2. Not all testers actually file bug reports. The cause may be that they find
the whole process to be too difficult, or they do not think it is worth the
effort. Perhaps the time between bug filing and the assignment is too long.
We also discussed the art work for a new release. It is common for the final
version of the graphics to become ready late in the cycle, which means that for
much of the testing, it is impossible to distinguish at a glance what version is
running.
If anyone has any suggestions on how we can get more testers involved at an
earlier stage, or any other ideas on how testing can be improved, please send
them to us. Remember, it is only about a month until 12.2 MS1 is released. As it
is likely that SystemV will disappear in 12.2, it is critical that your systemd
issues be resolved before August when the final version of 12.2 is released. A
testing version of systemd (37-317.1 from OBS) has fixed my one system that
failed to boot with systemd.
The next meeting of the TCT will be on Monday, January 16, 2012 at 18:00 UTC on
Channel #opensuse-testing on the Freenode IRC Network
(irc://irc.freenode.net/opensuse-testing).
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-testing+owner(a)opensuse.org
Lars Müller wrote:
> On Thu, Dec 15, 2011 at 07:24:08PM +0100, Per Jessen wrote:
>> Lars Müller wrote:
>>
>> > On Thu, Dec 15, 2011 at 10:04:01AM -0500, James Knott wrote:
>> >> Andreas Jaeger wrote:
>> >> >It will, the issues that came up now are getting fixed. Seems not
>> >> >enough people tested it before the release in earnest ;-(
>> >>
>> >> When you make a significant change, such as this, you'd better do
>> >> a *LOT* of testing before inflicting it on innocent users.
>> >
>> > Yes, you as the community have to test more and better. It's a
>> > shame how bad you performed as part of the openSUSE 12.1 release
>> > process. ;)
>>
>> How about we delay a release until it's been properly tested?
>
> Then we'll not see any further release.
Probably quite true, but also a pretty damning statement about the state
of our community. If the community is responsible for the testing, and
doesn't fullfil that task, we will have poor quality releases for as
long as we have changes. Therefore, if we want more testing and better
quality releases, we have to improve the community's involvement. I
think we do that by showing how much the community means.
<soapbox>
If we were to make releases dependent on the amount of testing done by
the community, we would show exactly how much we value the community.
</soapbox>
> What would be the benefit of additional three months? Three further
> months the same people would test it while the same other gang waits
> for the final release.
Yes, quite likely the initial state of things, but OTOH, if it is clear
to everyone that a test-scenario, for instance "postfix", is delaying
release because it is short of a few tests, it might just inspire more
testers.
> If you see real steps beyond a general delay of some weeks or months
> how to drive this better I'm sure all are happy to enhance the
> process.
See above. I have made similar proposals before, but noone is really
interested in discussing the lack of organisation of our QA process.
A general delay is unavoidable certainly to begin with, but what is the
hurry? None of the "I just can't wait" people have to wait for the
release, there is always factory and snapshots.
/Per
--
Per Jessen, Zürich (5.9°C)
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-testing+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
the 41st openSUSE Testing Core Team IRC Meeting will be on:
Monday, December 12th, 2011 at 18:00:00 UTC
Please use the following link to find out what that means in your local
timezone
http://www.timeanddate.com/worldclock/fixedtime.html?month=12&day=12&year=2…
We will meet in the Channel #opensuse-testing on the Freenode IRC
Network. irc://irc.freenode.net/opensuse-testing
Please post your topics on
http://en.opensuse.org/openSUSE:Testing_meeting
Best wishes,
Holgi
-----BEGIN PGP SIGNATURE-----
iEYEARECAAYFAk7WEgEACgkQ539IWoEy06W58gCfQG2UjDsDaovovp6YaiKuaoJj
N/sAn0DSB+l7fAgzsBGG3omTLYEBF2lQ
=m+L9
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-testing+owner(a)opensuse.org
The next meeting of the Testing Core Team will be Monday, December 12, 2011 at
18:00 UTC on Channel #opensuse-testing on the Freenode IRC Network
(irc://irc.freenode.net/opensuse-testing).
At this meeting, we will be discussing the openSUSE 12.1 release cycle and
analyzing what went well, what could have been improved, etc. If you have any
thing to contribute to this discussion, please join us. Remember, this is a
community distro.
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-testing+owner(a)opensuse.org
Hi List
With version OpenSuse 11.4 I've been working with the program SweetHome ( http://www.sweethome3d.com/ ), but now with version 12.1 the program does not work.
I do not know if it's a java problem or execute permissions.
Has anyone tried it?
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-testing+owner(a)opensuse.org