[Pkg-salt-team] Regression in 0.17.0

[Joe Healy]

Hi Andrii,

On Tue, Oct 08, 2013 at 12:17:01PM +0300, Andrii Senkovych wrote:
> Hi guys,
> 
> There is a severe regression in 0.17.0 that touches specifically
> Debian-based distros. The details of the issue are available on upstream
> bugtracker[1]. I'm going to fix things by reverting exactly this part until
> the upstream fix is released.

I agree this one is painful. I recommend setting the minion id
explicitly. I'm also thinking about making the minion id a debconf
setting (at a low priority) along with the master address (at a
slightly higher priority). I'm interested in your and others thoughts
on this.

In my experience, the early upstream releases ie 0.x.0 through roughly
0.x.2 often have regressions.

Have you (or anyone else) have any suggestions for how we best deal
with these releases in general?

1) Do we skip them?
2) Do we avoid uploading them to the main archive/backports?

The downside to skipping them is there is less testing in a range of
environments...

So far, I've been uploading to unstable and making backports available
at debian.saltstack.com, but am only backporting to the main archive
(wheezy-backports and squeeze-backports-sloppy) when the releases
reach a certain level of stability.

Additionally, (and partly) due to the fairly fast release schedule,
I've only patched the issues that really cause breakage (ie salt-ssh
not working at all) so that upstream will deal with the issues
properly.

I'll upload any changes you make to debian.saltstack.com as well and
backport to wheezy and squeeze there.

Any thoughts are most welcome.

Thanks,

Joe

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-salt-team/attachments/20131008/a1ddea56/attachment.sig>