[opensuse-factory] a checkin timeout before an Alpha release?
Would it be possible to have a 'new version' checkin timeout before an alpha release of the Factory? It seams that there are too many new checkins that break Factory lately. It would be nice if there were a short window before an alpha release where only bug fixes were checked in. I realize that the point of Factory is to keep current with the latest software, but a short period of stabilization before a release does not sound unreasonable to me Toni ------------------------------------------------------------------- Toni Harbaugh-Blackford Advanced Biomedical Computing Center (ABCC) National Cancer Institute ________________________________________________________________________ More new features than ever. Check out the new AIM(R) Mail ! - http://webmail.aim.com --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Dienstag 15 Januar 2008 schrieb Toni Harbaugh-Blackford:
Would it be possible to have a 'new version' checkin timeout before an alpha release of the Factory? It seams that there are too many new checkins that break Factory lately. It would be nice if there were a short window before an alpha release where only bug fixes were checked in.
I realize that the point of Factory is to keep current with the latest software, but a short period of stabilization before a release does not sound unreasonable to me
There is a short period. Friday is the deadline, the alpha is released thursday the week after. More of a freeze is unacceptable during alpha phase. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, 2008-01-15 at 13:50 +0100, Stephan Kulow wrote:
Am Dienstag 15 Januar 2008 schrieb Toni Harbaugh-Blackford:
Would it be possible to have a 'new version' checkin timeout before an alpha release of the Factory? It seams that there are too many new checkins that break Factory lately. It would be nice if there were a short window before an alpha release where only bug fixes were checked in.
I realize that the point of Factory is to keep current with the latest software, but a short period of stabilization before a release does not sound unreasonable to me
There is a short period. Friday is the deadline, the alpha is released thursday the week after. More of a freeze is unacceptable during alpha phase.
Except that we've had limited testing of factory because of the disk
outage. It would be nice to have that back for a day or two before we
burn the iso.
-JP
--
JP Rosevear
Am Dienstag 15 Januar 2008 schrieb JP Rosevear:
Except that we've had limited testing of factory because of the disk outage. It would be nice to have that back for a day or two before we burn the iso.
Factory wasn't installable yesterday anyway due to too many perl packages not yet building. And I won't move the release into the weekend. If alpha1 on regular schedule fails, we'll move to next week. But so far my testing looks pretty good. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 15 January 2008, JP Rosevear wrote:
There is a short period. Friday is the deadline, the alpha is released thursday the week after. More of a freeze is unacceptable during alpha phase. Except that we've had limited testing of factory because of the disk outage.
Factory was synced out before that.
It would be nice to have that back for a day or two before we burn the iso.
failed_packages gnome-maintainers | wc -l 43 I don't think that factory testing is the issue. Greetings, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, Jan 15, 2008 at 07:24:14AM -0500, Toni Harbaugh-Blackford wrote:
Would it be possible to have a 'new version' checkin timeout before an alpha release of the Factory? It seams that there are too many new checkins that break Factory lately. It would be nice if there were a short window before an alpha release where only bug fixes were checked in.
I realize that the point of Factory is to keep current with the latest software, but a short period of stabilization before a release does not sound unreasonable to me
Hmm, maybe it's too early for a new alpha? With some packages broken
since the update to gcc43 (like pdftk, compiling mplayer) it might
be a good idea to get at least the distro to compile completely again
before an alpha? (ok, mplayer isn't part of the distro, it's just
dear to me :-) So maybe sync out a gcc update that fixes these issues
and get everything to compile again before a new alpha?
ciao
Joerg
--
Joerg Mayer
JP Rosevear wrote:
On Tue, 2008-01-15 at 13:50 +0100, Stephan Kulow wrote:
Am Dienstag 15 Januar 2008 schrieb Toni Harbaugh-Blackford:
Would it be possible to have a 'new version' checkin timeout before an alpha release of the Factory? It seams that there are too many new checkins that break Factory lately. It would be nice if there were a short window before an alpha release where only bug fixes were checked in.
I realize that the point of Factory is to keep current with the latest software, but a short period of stabilization before a release does not sound unreasonable to me
There is a short period. Friday is the deadline, the alpha is released thursday the week after. More of a freeze is unacceptable during alpha phase.
Except that we've had limited testing of factory because of the disk outage. It would be nice to have that back for a day or two before we burn the iso.
-JP
Do I detect a single point of failure here? I would at least expect a couple of modest RAID systems with multi-pathing to prevent a disk outage, taking into account that the mirrors also depend on the system being up 24x7. Egg on PHBs' faces who no doubt reckoned this system is non-critical. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Dienstag 15 Januar 2008 schrieb Sid Boyce:
Do I detect a single point of failure here? I would at least expect a couple of modest RAID systems with multi-pathing to prevent a disk
Read opensuse-announce - the RAID system is exactly what died. For everything else you can easily join as sponsor, we'd even add you to the top page Greetings, Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Dienstag 15 Januar 2008 schrieb Joerg Mayer:
On Tue, Jan 15, 2008 at 07:24:14AM -0500, Toni Harbaugh-Blackford wrote:
Would it be possible to have a 'new version' checkin timeout before an alpha release of the Factory? It seams that there are too many new checkins that break Factory lately. It would be nice if there were a short window before an alpha release where only bug fixes were checked in.
I realize that the point of Factory is to keep current with the latest software, but a short period of stabilization before a release does not sound unreasonable to me
Hmm, maybe it's too early for a new alpha? With some packages broken since the update to gcc43 (like pdftk, compiling mplayer) it might
We switched to gcc43 in november. How long do you suggest we wait for someone to help the pdftk maintainer? Greetings, Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, 2008-01-15 at 14:31 +0100, Dirk Mueller wrote:
On Tuesday 15 January 2008, JP Rosevear wrote:
There is a short period. Friday is the deadline, the alpha is released thursday the week after. More of a freeze is unacceptable during alpha phase. Except that we've had limited testing of factory because of the disk outage.
Factory was synced out before that.
Except its not accessible for update on the opensuse servers, the raid server died in the middle of my update yesterday.
It would be nice to have that back for a day or two before we burn the iso.
failed_packages gnome-maintainers | wc -l 43
Thats all packages on all distros, there are many less on factory (17 I think, and not all are distributable either).
I don't think that factory testing is the issue.
I don't follow your point, even with packages failing factory helps you
test and determine ahead of time how good an alpha would be.
-JP
--
JP Rosevear
Stephan Kulow wrote:
Am Dienstag 15 Januar 2008 schrieb Sid Boyce:
Do I detect a single point of failure here? I would at least expect a couple of modest RAID systems with multi-pathing to prevent a disk
Read opensuse-announce - the RAID system is exactly what died. For everything else you can easily join as sponsor, we'd even add you to the top page
Greetings, Stephan
That's an excellent challenge, I'd like to start with $150 US. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tuesday 15 January 2008, JP Rosevear wrote:
I don't think that factory testing is the issue. I don't follow your point, even with packages failing factory helps you test and determine ahead of time how good an alpha would be.
Sure, my point is that the testing such a snapshot is not very meaningful because it is just one arbitrary state during a rapidly changing time period. Also, as you know, factory syncing to the outside is staged ("slowed down") to not stress mirrors even more. It IMHO makes more sense to take care of failing packages to ensure a consistent state for Alpha1 than testing one arbitrary snapshot in time that can not be recreated. But it's your time after all :) Greetings, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Tue, Jan 15, 2008 at 06:27:04PM +0100, Dirk Mueller wrote:
I don't think that factory testing is the issue. I don't follow your point, even with packages failing factory helps you test and determine ahead of time how good an alpha would be.
Sure, my point is that the testing such a snapshot is not very meaningful because it is just one arbitrary state during a rapidly changing time period.
Also, as you know, factory syncing to the outside is staged ("slowed down") to not stress mirrors even more. It IMHO makes more sense to take care of failing packages to ensure a consistent state for Alpha1 than testing one arbitrary snapshot in time that can not be recreated. But it's your time after all :)
I fully agree here: I don't expect everthing in an alpha to work, but I
expect the alpha to be *consistent* at the rpm layer: A big don't should
be that there are still packages that are suse 10.3.1. If they don't build,
then remove them or fix them but don't let them be part of a release. The
same is true for packages that no longer have their dependencies
fulfilled (e.g. pdftk requires a lib that has been replaced by a newer
version). Again: Remove those packages or fix them, but don't ship them.
If you really want to ship a system with inconsistent dependencies then
please call it snapshot and not (alpha) release. A missing package is much
better than a package with missing dependencies.
Calling something an (alpha/beta) release should have a defined set of
criteria that it *must* fulfill and I'd like to see these criteria
defined somewhere. One criteria that comes to my mind for all types of
releases is that it must be possible to rebuild all the packages that
said release comprises of by using only packages from that release.
ciao
Joerg
--
Joerg Mayer
participants (6)
-
Dirk Mueller
-
Joerg Mayer
-
JP Rosevear
-
Sid Boyce
-
Stephan Kulow
-
Toni Harbaugh-Blackford