[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: pound



On Mon, 25 Jan 2016, Brian May wrote:
> So version 2.6-2+deb7u1~deb6u1 or 2.6-2~deb6u1?

Yes.

> I considered doing this, and adding a new entry to the end of the
> changelog, however was worried that this would mean the changelog
> wouldn't be in the correct incrementing version order.

That's expected with backports.

> If I get a good answer to this, I will consider updating the wiki
> page. (Assuming I can actually do so, in my attempts to create an
> account, I managed to completely block my access instead, it now tells
> me "You are not allowed to access this!" for all accesses - even with a
> different browser).

Usually this means that you just are not logged in. :)

> Yes. It is mostly bug fixes and several new features, such as SNI
> support. I did a diff, and compared.

OK.

> > Also in such cases you might want to try to invite users to test the
> > update before uploading... you might not get any feedback but at least
> > you did your best ot ensure the upgrade was safe for everybody.
> 
> Ok, so it seems you main concerns where:
> 
> (a) Not waiting long enough for feedback. How long is considered
> sufficient? I guess I should also CC the package maintainer too?

How long is a matter of appreciation. It depends on the urgency of the
fix, of your confidence in your own decision, etc. But I would say 3 to 4
days when there's no urgency... so that you are sure to cover more than
just a week-end where not everybody is available.

Yes, ccing the package maintainer is a good idea in most cases.

> (b) Not asking user's to test my update. Is it sufficient to ask on
> debian-lts, or should I ask in other places too?

Asking on debian-lts is enough.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/


Reply to: