Release plans?

[Dmitry V. Levin]

On Mon, Mar 12, 2012 at 08:00:46PM +0100, Denys Vlasenko wrote:
> On 03/12/2012 02:47 PM, Dmitry V. Levin wrote:
> >>>>> But I'd like to hear from Denys about PTRACE_SEIZE perspective first.
> >>>>> We surely won't release PTRACE_SEIZE_DEVEL code enabled by default because
> >>>>> the kernel API might change.
> >>>>
> >>>> I'm going to ask kernel people to drop PTRACE_SEIZE_DEVEL.
> >>>
> >>> The patch was submitted in February, but current v3.3-rc6-240-gc7b2855
> >>> still insists on PTRACE_SEIZE_DEVEL.  Is there a prospect to release
> >>> without PTRACE_SEIZE_DEVEL any time soon, or should we rather leave this
> >>> experimental code disabled in the next release?
> >>
> >> It's in linux-next git:
> > [...]
> >> Looks like this change will go into linux-3.4
> >
> > So it is not going to be in a released kernel this spring?
> 
> I guess not.

OK, let's release without USE_SEIZE enabled then.  There is a lot of
stuff waiting since 4.6, more than enough to justify a release.  It's
such a pity we didn't have a policy to update the NEWS file along with
committing noteworthy changes.

What version should this release be, 4.6.1 or 4.7?


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20120312/8aa5e339/attachment.bin>