On Wed, Jul 18, 2012 at 12:10 PM, Jan Pazdziora <jpazdzi...@redhat.com> wrote: > On Wed, Jul 18, 2012 at 10:49:04AM -0400, Paul Robert Marino wrote: >> I have noticed that we have gone past the expected release date set >> for spacewalk version 1.8 is there any updated ETA on when it it will >> be released. >> there are a lot of bug fixes in 1.8 that have not been back ported to >> 1.7 which are a show stoppers for many people. so I was wondering is > > While I agree that we fixed a decent amount of bugs, I'd hardly > describe them show stoppers in vast majority of the cases. Were any > of the bugs regressions against 1.6 that did not have a workaround? Well a good example of a show stopper is the fact that as far as I know there is still an issue in 1.7 that prevents you from properly registering virtual machines if you are using PostgreSQL as your database backend. This was fixed in 1.8 but never back ported to 1.7 also note it was a bug that didn't effect 1.6 it was a new bug introduced in 1.7 due to other compatibility fixes for PostgreSQL
> >> there an updated ETA? > > No updated ETA. My personal estimate is two to three months. > >> Is there a list of what still needs to be >> completed? > > >From the list on the 1.8 milestone page, we have yet to see some > patch for the systemd feature. From things not on the list, the > latest cobbler packages in Fedoras and EPEL made Spacewalk > unusable. Since upgrade to the next Spacewalk version includes yum > upgrade, people would pick the latest cobbler package and ruin their > installations. We want to avoid sending people that path. The Cobbler issue is a massive problem I agree although that can easily be worked around by excluding cobbler in the yum configuration. that being said it may also be prudent to put a copy of the older version of cobbler in the spacewalk repo for the time being. For systemd I thought I saw that get added some time ago but if not if someone could put together a bullet list of what needs to be done I will be happy to see if there are any parts I can tackle to help move this along. > >> Is there a list of what needs testing so we can help >> further this along? > > Features listed on the 1.8 page, as well as all the MODIFIED / ON_QA > bugzillas. It would sure be nice to see community chime in with > feedback about Spacewalk nightly stability. Ill see about setting up a development 1.8 box latter this week > > Please note that the ABRT support is in the Spacewalk nightly yum > repos as of ten minutes ago, so people are welcome to start testing > that. > > -- > Jan Pazdziora > Principal Software Engineer, Satellite Engineering, Red Hat > > _______________________________________________ > Spacewalk-devel mailing list > Spacewalk-devel@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-devel _______________________________________________ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
