-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare for release mc-4.8.20 #3780
Comments
|
src/filemanager/panelize.c has unused "#define LABELS 3". Credit goes to "Andreas Mohr <and@gmx.li>" (this is from #2942). |
|
|
I tidy up OBS build testing across some linux distributions
mc-git_cleanup-*-default is current cleanup branch (3780_cleanup)
minor distributions failed with
|
|
|
mc-3780-tar.c-Cleanup-compiler-aggressive-loop-optimizations-warning.patch: applied as fixup. |
At current moment, the 3780_cleanup branch has 20 commits. I think it's time to review and merge it. |
Hi guys,
What do you think about a release real soon? It's been half a year since the last one.
Way back on May 7 I wrote on mc-devel: "this timestamp issue plus the pending mcview growing issues [...] are I believe a good reason to schedule a .20 release for the not-so-distant future (let's say, within a month or so)"
wiki/ReleaseGuidelines says "Period of releases: two-three months", but, in fact, the pattern recently seems to be (with a few exceptions) one in the spring and one in autumn :) |
Hi Egmont,
I thought of all people you are pretty much aware of what the current situation is. Sure, I'm all for making releases more often, but I'm simply incapable of doing so, as my stress level keeps increasing year after year beyond what I thought was even possible. Therefore, I'm struggling to do at least two releases per year and no less, and indeed they fall on time periods immediately "after spring vacation" and "after fall vacation"...
Anyways, as you might have noticed, I've started trying to merge easy stuff in preparation for the fall release. I don't know what Andrew's plans are, would be good if he could comment on what he absolutely wants to get in before release. I was hoping to review his cleanup branch next weekend, and then check what else can be easily merged & make an RC.
There have been some annoying OS X build breakage stuff on GitHub and a few small things I was thinking of trying to process...
Z. |
Hi Andrew, many thanks for your patience and feedback! I think the important thing is to finally get the cleanup in, then update translations and co., and then I will try my best to look into the other 2 things you mentioned. |
@yury, sorry, I didn't want to urge you... in fact, when I started typing my comment I hadn't yet realized the twice-a-year pattern :) By the time I finished writing the comment, I didn't think it through that there'll be a release soon anyways :)
Sure, let's wait for everyone's pet peeve bugs to get fixed first.
Thanks a lot again to all of you guys!
PS. I've updated the wiki about the release frequency. |
I was just about to ping you guys :) It's been a pretty quiet month, which hopefully means mc is quite stable. Hopefully all the changes got enough testing. Perfect time for a release :-)
#3850 has an accepted change, maybe it's okay to squeeze in that (but then it won't get enough testing, so maybe we should just delay it). I'd prefer you (andrew_b) to make the decision here. #3148 has been broken for a long time and doesn't have a fix yet, I fully agree that we shouldn't wait for it. |
RC out: https://mail.gnome.org/archives/mc/2017-November/msg00001.html |
done
done
done
done
done
done
done
done
done
done
done
https://www.midnight-commander.org/nopaste/tarball/
|
|
|
|
done
done
done
done
done |
done |
Important
This issue was migrated from Trac:
zaytsev
(@zyv)egmont
(@egmontkob)Note
Original attachments:
and
onMay 10, 2017 at 21:17 UTC
and
onMay 11, 2017 at 14:22 UTC
and
onMay 11, 2017 at 15:30 UTC
The text was updated successfully, but these errors were encountered: