On 23.03.2015 18:00, Grant Gainey wrote: > Hey folks, > > It has been a while since Spacewalk 2.2 went out, and we think the current > state of -nightly is a reasonable release-candidate for Spacewalk 2.3. > > Over the next week or so we will be doing a lot of testing and release-work. > If anyone would like to help with testing/verification/QE, that would be > wonderful - there are a lot of changes, and more eyes is always good. > > The list of BZs that need QE attention is: > > https://bugzilla.redhat.com/buglist.cgi?bug_status=ON_QA&classification=Community&list_id=3336542&product=Spacewalk&query_format=advanced > > I will wait to create the SPACEWALK-2.3 branch in git until after we've had a > chance to review automation failures and see successful installation and > upgrade testing. Once the branch is created, there is still a lot of > release-nanny work to be done, but we are working towards having 2.3 be > 'official' Real Soon Now <tm>. > > Thanks for everyone's help and contributions! > > Grant
Hi all, yes, the overall status of nighly is quite good and I am running it successfully in parallel to an RHEL 6 spacewalk 2.2 installation. Thx everyone :) But the following bugs should be considered for 2.3 release: RHEL7 related: Bug 1169674 - SWnightly@RHEL7: Error: Package: spacewalk-taskomatic-2.3.94-1.el7.noarch Requires: cglib < 2.2 Bug 1205167 - Move files shared between osad and osa-dispatcher to its own package Upgrade path: Bug 1205113 - obsoleted spacewalk-monitoring packages are not removed on upgrade Bug: Bug 1205108 - No Config diffs shown in webui on recent 2.3/nightly Best regards Patrick -- Lobster SCM GmbH, Hindenburgstraße 15, D-82343 Pöcking HRB 178831, Amtsgericht München Geschäftsführer: Dr. Martin Fischer, Rolf Henrich _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
