Announcing 389 Directory Server version 1.2.10.4 Stable
by Rich Megginson
The 389 Project team is pleased to announce the release of
389-ds-base-1.2.10.4. This release contains a fix for a bug that causes
the directory server to hang when using compare operations with virtual
attributes. No new features were added after alpha 8, just many bug
fixes. There are also 389-adminutil, 389-admin, and 389-dsgw packages.
NEW: EL6 support
Beginning with RHEL 6.2, the 389-ds-base package is included in the base
OS. Therefore, the 389-ds-base package can no longer be provided via
EPEL, due to RHEL/EPEL packaging restrictions.
However, the 389 Project will still make the full 389-ds-base package
available via http://repos.fedorapeople.org/repos/rmeggins/389-ds-base.
See http://directory.fedoraproject.org/wiki/Download for more information.
NEW: Issue Tracking System
We have moved our ticket tracking system from the Red Hat Bugzilla
https://bugzilla.redhat.com/enter_bug.cgi?product=389 to our Fedora
Hosted Trac https://fedorahosted.org/389. All of the old 389 bugs have
been copied to Trac. All new bugs, feature requests, and tasks should be
entered in Trac
This link shows all of the issues fixed in the 1.2.10 branch -
https://fedorahosted.org/389/report/12
In addition to the tickets for Milestone 1.2.10.3 there were a couple of
issues found by valgrind that have been fixed.
NEW: Plugin Authors
WARNING: Plugins should be made transaction aware so that they can be
called from within a backend pre/post transaction plugin. Otherwise,
attempting to perform an internal operation will cause a deadlock. See
http://directory.fedoraproject.org/wiki/Plugins
Installation
yum install --enablerepo=updates-testing 389-ds
# or for EPEL
yum install --enablerepo=epel-testing
[--enablerepo=epel-testing-389-ds-base] 389-ds
setup-ds-admin.pl
Upgrade
yum upgrade --enablerepo=updates-testing 389-ds-base
idm-console-framework 389-admin 389-ds-console 389-admin-console
389-dsgw 389-adminutil
# or for EPEL
yum upgrade --enablerepo=epel-testing
[--enablerepo=epel-testing-389-ds-base] 389-ds-base
idm-console-framework 389-admin 389-ds-console 389-admin-console
389-dsgw 389-adminutil
setup-ds-admin.pl -u
How to Give Feedback
The best way to provide feedback is via the Fedora Update system.
* Go to https://admin.fedoraproject.org/updates
* In the Search box in the upper right hand corner, type in the name of
the package
* In the list, find the version and release you are using (if you're not
sure, use rpm -qi <package name> on your system) and click on the release
* On the page for the update, scroll down to "Add a comment" and provide
your input
Or just send us an email to 389-users(a)lists.fedoraproject.org
Reporting Issues
https://fedorahosted.org/389
More Information
* Release Notes - http://port389.org/wiki/Release_Notes
* Install_Guide - http://port389.org/wiki/Install_Guide
* Download - http://port389.org/wiki/Download
12 years, 1 month
Test Day 2012-03-29: GNOME Shell Software Rendering
by Kamil Paral
There will be a "GNOME Shell Software Rendering" Test Day on Thursday!
https://fedoraproject.org/wiki/Test_Day:2012-03-29_Gnome_Shell_Software_R...
Here's an introduction from Vitezslav Humpa, who's in charge of this event from QA perspective:
This week brings a second installment of Fedora Test Day targeting GNOME 3. This time we will focus on software rendering providing a full GNOME session purely by means of the CPU. Nowadays with most of personal computers capable of hardware 3D acceleration this might seem unnecessary. But let's not forget a whole lot of us who have capable but yet unsupported hardware and get stuck with the Fallback mode.
And this is not the only case. In addition to computers with obsolete graphics there are VM hypervisors like KVM or VirtualBox that don't support full 3D yet. Fedora can also run on many kinds of less usual devices like tablets or netbooks that don't have free (or even proprietary) drivers ready.
Simply said, our goal is to make sure that no matter what hardware you are running your Fedora on, you will always get the user experience you are entitled to - a full GNOME desktop.
Do you have an older PC? Netbook? Or do you like to play with the latest of the latest in VM, where it won't "break" your computer? Even if not, please help us test the GNOME Shell software rendering by following few test cases and catching a few bugs - after all, as always with Fedora, you'll be doing that for yourself :-)
Date: 2012-03-29
Time: all day
What: https://fedoraproject.org/wiki/Test_Day:2012-03-29_Gnome_Shell_Software_R...
Where: #fedora-test-day
12 years, 1 month
Kdump Test Day on Mar 27
by Hongqing Yang
Greetings,
Today is the another test day for Fedora 17 Beefy Miracle. All the events
take place in #fedora-test-day on Freenode IRC.
As always, the more testing we can get, the better. Kernel developers and QA
team members will be on hand to help with testing and debugging.
The testing is easy and there are full instructions on the wiki pages.
You don't need a Fedora account to do the testing or to file the results,
but you will need a Bugzilla account to file bugs.
To join in, just follow the test instructions, then add your results to
the table at the bottom of the page - there are instructions on how to do it.
You can join #fedora-test-day to chat with the QA team and the developers.
Please come along and help us make sure Fedora 17's success!
[1] https://fedoraproject.org/wiki/Test_Day:2012-03-27_Kdump
Hongqing
12 years, 1 month
2012-03-26 @ 15:00 UTC - Fedora QA Meeting
by Adam Williamson
# Fedora Quality Assurance Meeting
# Date: 2012-03-26
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
It's meeting time once more. We have a beta to sign off on, so expect
lots of happy fun blocker review. Also, I figured it'd be a good idea to
kick around the 'QA as a sub-project' topic in a meeting.
This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
https://fedoraproject.org/wiki/QA/Meetings/20120326
The current proposed agenda is included below.
== Proposed Agenda Topics ==
1. Previous meeting follow-up
2. Fedora 17 Beta status / blocker review
3. 'Project' status
4. Test Day report
5. Upcoming QA events
6. AutoQA update
7. Open floor
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
12 years, 1 month
Fedora 17 QA Retrospective page is up
by Adam Williamson
Hey, everyone. I'm sorry this is late, my bad for not getting it up
earlier. :(
The Retrospective page for Fedora 17 QA is now up:
https://fedoraproject.org/wiki/Fedora_17_QA_Retrospective
We use the retrospective page to track things that went well and things
that didn't go so well during the Fedora 17 validation process, and for
tracking ideas we have but don't have time to act on during the rush of
doing validation (that's the wishlist).
Please, add any feedback you have of this type to the retrospective
page! There are instructions on the page for adding feedback.
All feedback is useful, and once 17 validation is done, we'll take a
look at all the items on the page and come up with specific
recommendations for addressing them which we'll file as trac tickets and
work on in the time before Fedora 18 validation starts up. We've been
doing this for a while now and it's turned out to be a great way to keep
constantly improving our processes.
You can look at the previous pages for inspiration:
https://fedoraproject.org/wiki/Category:QA_Retrospective
And I'll copy/paste James' old list of leading questions to prompt
feedback (thanks, James!):
1. Were you able to participate in any Fedora 17 Alpha, Beta or
Final test runs?
2. What worked well, what prevented you from participating, were
instructions clear?
3. What worked (or didn't work) well about Fedora Test Days this
release?
4. Are you a maintainer, why do you think your critpath updates
haven't been tested? What could you do to encourage more
testing of your proposed updates?
5. Did you escalate any bugs for consideration as
{Alpha,Beta,Final} release Blockers? Why not? Was the process
well documented and did it make sense?
6. Did you attend or contribute to any Fedora blocker meetings?
Why not? What did you like, dislike? What prevented you from
participating?
7. Did you find any of the release criteria changes or validation
test extensions particularly useful or problematic?
8. Can you think of any obviously important areas we are not
currently covering in the validation tests and criteria?
9. Unlimited time and resource ... what do you think the the QA
team should focus on for Fedora 18 and beyond </pony>
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
12 years, 1 month
