389-announce January 2012

389-announce@lists.fedoraproject.org

1 participants
2 discussions

Announcing 389 Directory Server version 1.2.10 Alpha 8 Testing
by Rich Megginson 27 Jan '12

27 Jan '12

The 389 Project team is pleased to announce the release of 389-ds-base-1.2.10.a8. 1.2.10 has some new features and fixes for bugs found in 1.2.10 testing and bugs from earlier releases. There is also a 389-admin package in testing 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 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 # 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 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

1 0

Announcing 389 bugzilla is moving to 389 trac
by Rich Megginson 04 Jan '12

04 Jan '12

The 389 team will be switching to trac for keeping track of bugs/enhancement requests/issues instead of Red Hat Bugzilla. * Why? We needed a clear separation between "upstream" 389 development and "downstream" Red Hat product/process. It was getting too confusing using bugzilla for both upstream and downstream. We needed an issue tracking tool that was focused only on the upstream 389. Most of the other related groups such as freeipa, sssd, dogtag, and others have already moved to use trac. * What happens to 389 bugs in bugzilla? Nothing. They are still there. You can continue to use bugzilla. All of the open issues have been copied to trac. You can still use bugzilla to refer to the older issues. We have an internal tool we use that links bugzilla bugs to trac so we can find "unlinked" bugs/tickets and create links, copy bugs, etc. * What if I find an issue with a particular Fedora/EPEL release? Go ahead and file the bug in bugzilla against Product: Fedora or Fedora EPEL and Component: 389-ds-base (or whatever component). The 389 development team will triage the bug. If it affects upstream, we will copy it into a trac ticket. When we fix the bug and push out a package containing the fix, we will update the bugzilla bug, so if you don't care about what happens in the upstream, you don't have to worry about it. You can just pay attention to the bugzilla Fedora/EPEL bug and find out when a package containing the fix is released. * Where is the new trac? https://fedorahosted.org/389 * How do I see the tickets? https://fedorahosted.org/389/report - there are various reports to see tickets * How do I file a new ticket, or add myself to the CC list of an existing ticket? You must first have a Fedora Account - see https://admin.fedoraproject.org/accounts/ Once you login, you should see a link for New Ticket, and you should be able to modify/add comments to existing tickets.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-announce January 2012