On 10/21/2016 03:42 AM, Thierry Vignaud wrote:
On 20 October 2016 at 15:32, Panu Matilainen wrote:
After couple of weeks of headache from trying to sort this out somehow, here
comes 4.13.0 rc2.
As explained earlier [1], in order to get the release train back on track,
On 10/21/2016 12:09 PM, Thierry Vignaud wrote:
On 21 October 2016 at 08:51, Panu Matilainen wrote:
Please test and report any anomalies. From rc2 to final only regression fixes
will be allowed. Unless of course something really strange comes up, you never
know. Or I
Thanks for the patches. Added.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/95#issuecomment-255337922___
Rpm-maint mailing
Closed #95.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/95#event-831801071___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
ignatenkobrain commented on this pull request.
LGTM. Though I'm not sure how this will work with RPMs created before that
change.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
As of 57f94a582602f0353cdb17a02dc12c4461d4f32d, it's now possible
to have proper changelogs with dates and times properly set.
Thus, it makes sense to render this information by default.
You can view, comment on, or merge this pull request online at:
On Fri, 2016-10-21 at 12:33 +0300, Panu Matilainen wrote:
> On 10/21/2016 12:09 PM, Thierry Vignaud wrote:
> > On 21 October 2016 at 08:51, Panu Matilainen wrote:
> >
> Please test and report any anomalies. From rc2 to final only regression
> fixes will be allowed.
On 21 October 2016 at 11:33, Panu Matilainen wrote:
>>> Ah, I did run the test-suite but not from the created tarball. One more
>>> thing to remember when cutting releases. Or rather *cough* to document
>>> *cough*.
>>>
>>> Applied (with a slightly expanded comments).
>>
>>