On Mon, 23 Nov 2015 19:50:00 -0500
Stephen Gallagher wrote:
> A similar and more annoying problem is that mailman 3 lost the
> X-List-Administrivia header (and didn't replace it with anything at
> all), so all list administrators have no simple way to filter out the
> moderation queue messages.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/23/2015 04:08 PM, Kevin Fenzi wrote:
> On Mon, 23 Nov 2015 12:42:53 -0800 Adam Williamson
> wrote:
>
>> On Mon, 2015-11-23 at 11:35 -0800, Joshua Andrews wrote:
>>> Suddenly my message filters stopped working. I've been using
>>> "X-BeenThere:
The following Fedora 21 Security updates need testing:
Age URL
297 https://bodhi.fedoraproject.org/updates/FEDORA-2015-1467
openstack-glance-2014.1.3-4.fc21
177 https://bodhi.fedoraproject.org/updates/FEDORA-2015-9141
ceph-deploy-1.5.25-1.fc21
166 https://bodhi.fedoraproject.org/updat
I believe a failure to upgrade from N-2 to N should not block the N
release. The reason is limited resources, both for tests and for changes
to fix problems. These resources are more valuable applied to the N
release than to something two releases in the past.
If someone wants to test a release-
On Mon, 23 Nov 2015 12:42:53 -0800
Adam Williamson wrote:
> On Mon, 2015-11-23 at 11:35 -0800, Joshua Andrews wrote:
> > Suddenly my message filters stopped working. I've been using
> > "X-BeenThere:" in the message headers to filter list emails. Do I
> > need to create new filters, has X-BeenThe
On Mon, 2015-11-23 at 10:36 -0500, Kamil Paral wrote:
> Oh, one more thing - similarly to _bios and _uefi test cases, I'd
> like to change existing _workstation_encrypted test case to just
> _encrypted test case - it shouldn't matter which package set is
> installed to verify that there's no issue
On Mon, 2015-11-23 at 11:35 -0800, Joshua Andrews wrote:
> Suddenly my message filters stopped working. I've been using "X-BeenThere:"
> in the message headers to filter list emails. Do I need to create new
> filters, has X-BeenThere been obsoleted?
This is probably to do with the mailman3 update.
On Mon, 2015-11-23 at 13:26 -0500, Kamil Paral wrote:
> > I feel that for something as important as system upgrade, we should provide
> > a
> > better level of quality and assurance for upgrading across 2 releases.
> > Currently we have no criterion and testing it is just an afterthought, not
> >
==
#fedora-meeting: Fedora QA meeting
==
Meeting started by adamw at 16:00:05 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2015-11-23/fedora-qa.2015-11-23-16.00.log.html
.
Meeting summary
---
Suddenly my message filters stopped working. I've been using "X-BeenThere:"
in the message headers to filter list emails. Do I need to create new
filters, has X-BeenThere been obsoleted?
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/tes
> I feel that for something as important as system upgrade, we should provide a
> better level of quality and assurance for upgrading across 2 releases.
> Currently we have no criterion and testing it is just an afterthought, not
> even tracked anywhere. I'd like to amend the existing criterion to
Missing expected images:
Cloud disk raw i386
Cloud_atomic disk raw x86_64
Workstation live x86_64
Workstation live i386
Cloud disk raw x86_64
Kde live x86_64
No images in this compose but not Rawhide 20151122
Images in Rawhide 20151122 but not this:
Kde live x86_64
Failed openQA tests: 26 of 4
# Taskotron Outage and Upgrade
# Date: 2015-11-25
# Time: 21:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Length: Approximately 4 hours
There is a larger infra outage scheduled for Wednesday and we're going
to take advantage of that to do an upgrade to production Taskotron. Th
On Wed, 18 Nov 2015 16:36:16 -0800
Adam Williamson wrote:
> #2 MOAR METADATA
>
>
> The alternative is to make the existing Blocker trackers do more work.
> In this model we wouldn't add any new tracker bugs; we'd just add new
> 'magic words' in the Whiteboard field. Right now,
Our current upgrade criterion says:
"For each one of the release-blocking package sets, it must be possible to
successfully complete an upgrade from a fully updated installation of the
previous stable Fedora release with that package set installed."
https://fedoraproject.org/wiki/Fedora_24_Beta_R
> Now that we have system-upgrade instead of fedup, I don't think we need to
> split every single upgrade test case between bios and uefi, as we have it
> right now:
> https://fedoraproject.org/wiki/Template:Installation_test_matrix#Upgrade
>
> The difference is that fedup created its own upgrade
Compose started at Mon Nov 23 05:15:03 UTC 2015
Broken deps for i386
--
[IQmol]
IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0
IQmol-2.3.0
The following Fedora 22 Security updates need testing:
Age URL
227 https://bodhi.fedoraproject.org/updates/FEDORA-2015-5878
echoping-6.1-0.beta.r434svn.1.fc22
176 https://bodhi.fedoraproject.org/updates/FEDORA-2015-9185
ceph-deploy-1.5.25-1.fc22
109 https://bodhi.fedoraproject.org/upd
Now that we have system-upgrade instead of fedup, I don't think we need to
split every single upgrade test case between bios and uefi, as we have it right
now:
https://fedoraproject.org/wiki/Template:Installation_test_matrix#Upgrade
The difference is that fedup created its own upgrade environmen
> >> Well, here's our latest mess-up:
> >> https://bodhi.fedoraproject.org/updates/FEDORA-2015-e00b75e39f
> >> dnf-plugin-system-upgrade-0.7.0-1.fc22 had enough karma for stable
> >> on
> > Oct 29, which was Go/No-Go day. Therefore it was considered "resolved".
> >
> > "Had enough karma" != queued
20 matches
Mail list logo