Bug#856640: unblock: suricata/3.2.1-1
On Mon, 2017-03-06 at 19:06 +0100, Arturo Borrero Gonzalez wrote:
> On 4 March 2017 at 14:26, Salvatore Bonaccorso <carnil@debian.org> wrote:
> > Hi Adam,
> >
> > On Sat, Mar 04, 2017 at 11:56:23AM +0000, Adam D. Barratt wrote:
> >> On Fri, 2017-03-03 at 10:55 +0100, Moritz Muehlenhoff wrote:
> >> > Then it should not be in a stable release, but updated via stretch-updates.
> >>
> >> That's self-contradictory. -updates is a subset of proposed-updates, so
> >> any packages released via it are necessarily in stable.
> >
> > Not Moritz here, but maybe we can argue that way: It could be handled
> > like clamav (and be updated to upstream point updates via
> > stretch-updates), or possibly suricata should not be at all in a
> > stable release beeing to fast moving target[*].
> >
>
> After some thinking, yes. Upstream point updates via stretch-updates
> is probably the way to go.
It's not a given, however; doing so is extra work for both us and you,
and disruption for users, so we have to be sure that it's the best idea.
In order to consider that, we'd need some more information, for example:
- how often do upstream make point releases?
- do they just include bug fixes, or also new features?
- what severity of fixes are included?
- what sort of testing (preferably automated) does the code get before
release?
- what level of regressions are generally experienced with new releases?
Regards,
Adam
Reply to: