Bug Squashing Day - Tomorrow!

Support
1

Hi all,

The first Foreman bug squashing day will take place tomorrow! We'd
love to have as many people as we can trying to reproduce and squash
bugs over the course of the day. Here's a few details:

We'll be using IRC as the main communication. At least some of the
Foreman team will be paying attention to IRC to help with any issues.
In rough timezone order the team is:

  • ohadlevy
  • amos
  • josephmagen
  • Dominic
  • gwmngilfen
  • samkottler

Some of us should be around from ~7am GMT to Midnight GMT.

We've created a list of bugs that we think need looking at. Some of
these need to be tested to see if they still occur in the latest code,
some are definitely present and need fixes, and some need just need
testing of an existing fix.

You can find this list at: http://theforeman.org/versions/show/23

If these all get done, firstly; awesome! However, there's no shortage,
so if this list runs out or there's nothing you think you can help
with, do look at the wider bug list for something to try.

If you make progress with a ticket, please update it so we don't
duplicate effort. If you've got a full fix, you can contribute in the
usual ways - a Github pull request is easiest.

Here's a few other tips that might be handy:

  • If you don't already have a Redmine account, please create one at
    http://theforeman.org
  • If you're going to set up a development instance of Foreman, see [1]
  • If you want to make sure the tests pass, see [2]

[1] Installing latest code - Foreman
[2] Test environment - Foreman

2

Hah, Looks like I missed this one. No wonder why I had an influx of emails today from tickets I created.

Thanks,

Corey Osman
corey@logicminds.biz

Green IT and Data Center Automation Specialist

··· On Nov 14, 2012, at 9:07 AM, Greg Sutcliffe wrote:

Hi all,

The first Foreman bug squashing day will take place tomorrow! We’d
love to have as many people as we can trying to reproduce and squash
bugs over the course of the day. Here’s a few details:

We’ll be using IRC as the main communication. At least some of the
Foreman team will be paying attention to IRC to help with any issues.
In rough timezone order the team is:

  • ohadlevy
  • amos
  • josephmagen
  • Dominic
  • gwmngilfen
  • samkottler

Some of us should be around from ~7am GMT to Midnight GMT.

We’ve created a list of bugs that we think need looking at. Some of
these need to be tested to see if they still occur in the latest code,
some are definitely present and need fixes, and some need just need
testing of an existing fix.

You can find this list at: http://theforeman.org/versions/show/23

If these all get done, firstly; awesome! However, there’s no shortage,
so if this list runs out or there’s nothing you think you can help
with, do look at the wider bug list for something to try.

If you make progress with a ticket, please update it so we don’t
duplicate effort. If you’ve got a full fix, you can contribute in the
usual ways - a Github pull request is easiest.

Here’s a few other tips that might be handy:

  • If you don’t already have a Redmine account, please create one at
    http://theforeman.org
  • If you’re going to set up a development instance of Foreman, see [1]
  • If you want to make sure the tests pass, see [2]

[1] Installing latest code - Foreman
[2] Test environment - Foreman