LTP release && Christmas && New year
Hi!
Christmas and New Year is getting closer so it's time to start preparing another release...
I will be on a time off since the next week so I propose to work on merging as many patches as possible this week. Then we will follow up with pre-release testing and freeze. I will join the effort once I return back to the work which will be Monday 2. 1. 2017. then we will do the release a week or two after that. Does that sound OK to everyone?
Signature · 2 lines
Cyril Hrubis [email protected]
----- Original Message -----
Quoted 9 lines
From: "Cyril Hrubis" <[email protected]>
To: [email protected]
Sent: Monday, 12 December, 2016 2:22:05 PM
Subject: [LTP] LTP release && Christmas && New yearHi!
Christmas and New Year is getting closer so it's time to start preparing another release...
Quoted 5 lines
I will be on a time off since the next week so I propose to work on merging as many patches as possible this week. Then we will follow up with pre-release testing and freeze. I will join the effort once I return back to the work which will be Monday 2. 1. 2017. then we will do the release a week or two after that. Does that sound OK to everyone?
Sounds good to me.
Regards,
Jan
Quoted 8 lines
--
Cyril Hrubis
[email protected]--
Mailing list info: https://lists.linux.it/listinfo/ltp
Hi!
Quoted 5 lines
I will be on a time off since the next week so I propose to work on merging as many patches as possible this week. Then we will follow up with pre-release testing and freeze. I will join the effort once I return back to the work which will be Monday 2. 1. 2017. then we will do the release a week or two after that. Does that sound OK to everyone?
And I'm back. I will try to do something about implicit function warnings on older distributions introduced by recent addition of pread(), pwrite() and getpgid() into the safe macros header, then do a few runs on different distros/hardware.
Is there anything that should be considered for a release?
I guess that we should merge the fix for aarch64 check in max_map_count test.
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 3 lines · Cyril Hrubis
I guess that we should merge the fix for aarch64 check in
max_map_counttest.
We could fix for aarch64 check in max_map_count by this patch:
[LTP] [PATCH v3] Fix mistake in strcmp() for skipping in aarch64
What's your opinion?
Thanks,
Cui Bixuan