Reminder: Bugzilla UPGRADE to 3.6 on August 13th 9:00 p.m.EDT [01:00 UTC]
by John Poelstra
Sending on behalf of Dave Lawrence. This will affect Fedora too.
REMINDER: Red Hat Bugzilla (bugzilla.redhat.com) will be unavailable on
August 13th starting at 9:00 p.m. EDT [01:00 UTC] to perform
an upgrade from Bugzilla 3.4 to Bugzilla 3.6. We are hoping to be
complete in no more than 5 hours barring any problems. Any
services relying on bugzilla.redhat.com may not work properly during
this time. Please be aware in case you need use of those
services during the outage.
Also *PLEASE* make sure any scripts or other external applications that
rely on bugzilla.redhat.com are tested against our test
server before the upgrade if you have not done so already (see original
email below). Let the Bugzilla Team know immediately of any
issues found by reporting the bug in bugzilla.redhat.com against the
Bugzilla product, version 3.6.
-------------------------------------------
Greetings,
The Red Hat Bugzilla team is happy to announce another public beta
release of the next version of Red Hat Bugzilla based on the
upstream 3.6 code base.
Please test drive at:
https://partner-bugzilla.redhat.com
Over the years Red Hat has made substantial customizations to Bugzilla
to fit into the Engineering
tool chain. Over time the upstream has incorporated some of these
customizations or solved them in different ways. Upgrading reduces
our customization footprint (and thus maintenance) while bringing many
bug fixes & enhancements.
The main area of focus for our public betas is stability. Functionality
that currently works in our 3.4 code base should continue to
work as expected in the new 3.6 release. These include various ajax
optimizations, needinfo actor support, frontpage.cgi, product
browser, several various UI enhancements, and of course the XMLRPC API.
Please feel free to point your various scripts and third party
applications that use the XMLRPC API at the test server to make sure
they continue to function properly.
There are numerous other changes behind the scenes that we haven't
listed. The goal is to make sure that functionality that people
have come to expect in 3.4 is possible in the new system.
There are also numerous new features/fixes that are part of the upstream
3.6 release. For more detailed information on what has
changed since the last release, check out the release notes page at
https://partner-bugzilla.redhat.com/page.cgi?id=release-notes.html .
The database is a recent snapshot of the live database so should be
useful for testing to make sure the information is displayed
properly and changeable. Also with a full snapshot it is possible to
test for any performance related issues. Email has been
disabled so that unnecessary spam is not sent out. So
feel free to make changes to bugs to verify proper working order.
We are asking for everyone to get involved as much as possible with
testing and feedback on the beta releases to help us make this
the most robust and stable release possible.
Please file any enhancement requests or bug reports in our current
Bugzilla system at https://bugzilla.redhat.com . File them under
the Bugzilla product and relevant component with the version 3.6. With
everyone's help we can make this a great release.
Thanks
The Red Hat Bugzilla Team
13 years, 7 months
Please help test 389 Directory Server 1.2.6 Release Candidate 7
by Rich Megginson
The 389 team is pleased to announce the availability of Release
Candidate 7 of version 1.2.6. This release has one bug fix.
WARNING: If you are upgrading from a previous 1.2.6 release candidate,
you will need to run fixfiles to fix some SELinux AVCs, or directory
server will not start. See bug
https://bugzilla.redhat.com/show_bug.cgi?id=622882
To fix, run this:
fixfiles -R 389-ds-base restore
WARNING: If you are upgrading from a 1.2.6 alpha or release candidate,
you will need to manually fix your entryrdn index files. See
http://directory.fedoraproject.org/wiki/Subtree_Rename#warning:_upgrade_f...
for more information. If you are upgrading from 1.2.5 or earlier, there
is no problem.
***We need your help! Please help us test this software.*** It is a
release candidate, so it may have a few glitches, but it has been tested
for regressions and for new feature bugs. The Fedora system
strongly encourages packages to be in Testing until verified and pushed
to Stable. If we don't get any feedback while the packages are in
Testing, the packages will remain in limbo, or get pushed to Stable.
The more testing we get, the faster we can release these packages to
Stable. See the Release Notes for information about how to provide
testing feedback (or just send an email to
389-users(a)lists.fedoraproject.org).
The packages that need testing are:
* 389-ds-base-1.2.6.rc7 - 389-ds-base
More information
* Release Notes - http://port389.org/wiki/Release_Notes
* Install_Guide - http://port389.org/wiki/Install_Guide
* Download - http://port389.org/wiki/Download
=== Bugs Fixed ===
This release contains several bug fixes. The complete list of bugs
fixed is found at the link below. Note that bugs marked as MODIFIED
have been fixed but are still in testing.
* Tracking bug for 1.2.6 release -
https://bugzilla.redhat.com/showdependencytree.cgi?id=543590&hide_resolved=0
** Bug 621928 - Unable to enable replica (rdn problem?) on 1.2.6 rc6
13 years, 7 months
Please help test 389 Directory Server 1.2.6 Release Candidate 6
by Rich Megginson
The 389 team is pleased to announce the availability of Release
Candidate 6 of version 1.2.6. This release has several bug fixes.
Note: RC4 and RC5 were never released.
***We need your help! Please help us test this software.*** It is a
release candidate, so it may have a few glitches, but it has been tested
for regressions and for new feature bugs. The Fedora system
strongly encourages packages to be in Testing until verified and pushed
to Stable. If we don't get any feedback while the packages are in
Testing, the packages will remain in limbo, or get pushed to Stable.
The more testing we get, the faster we can release these packages to
Stable. See the Release Notes for information about how to provide
testing feedback (or just send an email to
389-users(a)lists.fedoraproject.org).
The packages that need testing are:
* 389-ds-base-1.2.6.rc6 - 389-ds-base
* 389-admin-1.1.11.rc2 - 389-admin
More information
* Release Notes - http://port389.org/wiki/Release_Notes
* Install_Guide - http://port389.org/wiki/Install_Guide
* Download - http://port389.org/wiki/Download
=== Bugs Fixed ===
This release contains several bug fixes. The complete list of bugs
fixed is found at the link below. Note that bugs marked as MODIFIED
have been fixed but are still in testing.
* Tracking bug for 1.2.6 release -
https://bugzilla.redhat.com/showdependencytree.cgi?id=543590&hide_resolved=0
** Bug 617013 - repl-monitor.pl use cpu upto 90%
** Bug 616618 - 389 v1.2.5 accepts 2 identical entries with different DN
format
** Bug 547503 - replication broken again, with 389 MMR replication and
TCP errors
** Bug 613833 - Allow dirsrv_t to bind to rpc ports
** Bug 612242 - membership change on DS does not show on AD
** Bug 617629 - Missing aliases in new schema files
** Bug 619595 - Upgrading sub suffix under non-normalized suffix disappears
** Bug 616608 - SIGBUS in RDN index reads on platforms with strict
alignments
** Bug 617862 - Replication: Unable to delete tombstone errors
** Bug 594745 - Get rid of dirsrv_lib_t label
13 years, 7 months