spacemacs作者准备要弃坑啦？

Peter-Chou · 2019 年1 月 4 日 06:02

Help needed to prepare the 0.300 release

opened 08:34PM - 21 Dec 18 UTC

closed 10:41AM - 13 Jan 19 UTC

High Priority Help wanted

In order to prepare the next release we need to have all the commits merged in s…ince the last release summarized into the changelog. This process is a one time thing, as we plan to integrate it as part of our merge process in the future, but now it needs to be done manually. We started working towards this on the [release_notes_0.300](https://github.com/syl20bnr/spacemacs/tree/release_notes_0.300) branch. You can see an example in this commit: https://github.com/syl20bnr/spacemacs/commit/8cf612771bf494b2249bda68800a80e948fd194b. There are `1418` commits left to summarize, about one and a half year's worth of merges. How we've done it so far was to pin a specific commit (69a89cc41243cfb189238a2297fde4498d7fcf6d) and navigate the github log pages until the first commit that was not summarized. Currently we are at this page: https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1418 Notice the query parameter in the url: `before=69a89cc41243cfb189238a2297fde4498d7fcf6d` tells it from which commit to start pagination and `+1418` tells it how many commits we've progressed. There are 35 commits per page and it takes us 30-40 minutes to summarize one page, depending on what the commits changed. As there are not many of us able to work on this, and because it's taking a long time, we were thinking of crowd-sourcing this activity in the following way: - At the bottom of this post there will be a list of all the pages not yet summarized. - Reserve one page per person at a time, starting from top to bottom. Please do not skip pages as it makes it more difficult to track. - Summarize all the commits on that page in the `CHANGELOG.develop` file and open a PR against the `release_notes_0.300` branch. - You can reserve another page while waiting to get merged but open a separate PR with it. It's easier to review this way. - One of the maintainers will assign themselves to that PR, review and merge it. - Please specify which page and from which commit you start in the body and add a pointer to the next page and commit: ``` Summarizing: https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1418 Starting with: cb17b2773badb4a86e0ffc1b366e5b8589cbea66 New pointer: https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1383 Start with: 106f98497ea91730cb53ece1733d87bf7fae2e51 ``` - Don't forget to add your name in the `Release notes summarized` section if you wish to. - If you can not finish a page in the same day, please release it so that somebody else can pick it up. - If it's unclear where exactly to put something, ask about it in the PR. Here are some guidelines: * Any breaking change goes in `*** Breaking Changes`. * Changes to the core (the `core/` directory) go in the `*** Core changes` section. * Changes to the spacemacs distributions and spacemacs layers go in the `*** Distribution changes` section. * Documentation fixes, code style changes and CI are grouped at the end. * Changes to a newly added layer should not be added in a new entry, instead put the contributor name together with the person that added the layer. * Everything else should be under it's specific layer. * Look at the previously summarized commits if you want to see an example of a specific element. - For each change you can use the commit title as a summary, but make sure to edit it in case it does not make sense, or if you need to add extra/less detail. - At the end of the summary add `(thanks to ` and the person's name. Make sure to use the person's real name if available, otherwise use the github username. If all else fails, there will be a name in the commit itself that you can use. - If you notice that a commit builds on top of an existing one you can group those together. - If one of the maintainers (@syl20bnr @bmag @d12frosted @TheBB @JAremko @sdwolfz) did a trivial change to one of the already summarized commits, like adding documentation, code formatting or moving stuff around, you can skip over it, but not if it was done by a contributor. - It is not necessary to mention @syl20bnr How to reserve: - Look in the list below for the first open entry. - Search for it in this thread and see if it was not reserved in the last 24 hours and it does not have an associated PR open. - Announce that you reserve it by posting: ``` Reserving: https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1418 ``` - Once you open a PR edit your post to say: ``` Reserving: https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1418 PR: #8550 ``` Here is a list of all the pages, the ticked ones are already done `40/40`: - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1418 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1383 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1348 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1313 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1278 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1243 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1208 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1173 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1138 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1103 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1068 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+1033 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+998 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+963 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+928 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+893 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+858 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+823 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+788 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+753 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+718 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+683 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+648 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+613 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+578 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+543 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+508 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+473 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+438 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+403 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+368 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+333 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+298 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+263 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+228 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+193 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+158 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+123 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+88 - [x] https://github.com/syl20bnr/spacemacs/commits/develop?before=69a89cc41243cfb189238a2297fde4498d7fcf6d+53 Note that these are not actually all the commits, there are still some left on the develop branch. We will take care of those at the end. Also there are some bug fixes that we'll need to do just before merging, so we'll end up making sure everything works for a few more days after we finish this mammoth of a task. Happy hacking and thank you for the help! -------- _edited by @syl20bnr to mention that it is not necessary to credit Sylvain Benner_ -------- Thank you everybody for participating in this :heart:! Your effort made a huge difference as this would have taken us 2-3 more months to finish on our own. Now we can focus on all the remaining regressions until we release as scheduled at the end of the month.

是不是作者觉得这个项目已经变成beast了，准备弃疗了？

iab · 2019 年1 月 4 日 06:13

spacemacs 被包装的面目全非了，根本看不懂

Peter-Chou · 2019 年1 月 4 日 06:16

哈哈我压根就没看过spacemacs的核心代码，只是layer里的几个el文件看看，只是这代码量已经蛮吓人了

ReimuXMX · 2019 年1 月 4 日 08:08

它的核心源码我根本不敢看……

henryt · 2019 年1 月 4 日 08:16

全靠spacemacs存活至今 ╮(╯_╰)╭

songpeng · 2019 年1 月 4 日 08:24

我理解应该不是，是指具体里面做CHANGE.develop 中标注contribution时的说明。

JJPandari · 2019 年1 月 4 日 09:28

楼主你这是什么理解，人家根本说起弃坑两个字……

Peter-Chou · 2019 年1 月 4 日 09:42

好吧我错啦 ~~~

et2010 · 2019 年1 月 4 日 10:22

spacemacs 短期内不可能倒掉。现在比较稳定倒是真的。前两天一个 ivy 的 update 导致报错，spacemacs 马上跟进进行了修复。而且 spacemacs 社区已经成型了，现在都是社区在维护。创始人的作用只在有重大架构改变，或者增加 breakthrough 级别的功能时才会体现。

cireu · 2019 年1 月 4 日 12:04

有点好奇是啥，ivy最近没引入breaking changes哇

seagle0128 · 2019 年1 月 10 日 15:59

恕我直言，spacemacs 和 emacs 基本属于两个东西了，不管是看起来还是用起来太费劲了~~~哲学思想都不同了

Peter-Chou · 2019 年1 月 11 日 01:09

哈哈，我感觉spacemacs作为其他编辑器与emacs之间的一个middle ground正好（不然直接从裸体emacs开始迁移太硬核了），spacemacs对于初上手emacs的人还是很省事的（可能到后期用熟了想要打造自己的emacs时就不合适）

seagle0128 · 2019 年1 月 11 日 06:39

说得也是，对初学者还是有利的。不过弊端是让初学者接触到的不是原生的 Emacs，而且多半培养成 VI党。spacemacs 配置都是按照自己的一套逻辑，用起来越来越笨重了，这也是我弃坑的重要原因。

Kinneyzhang · 2019 年1 月 11 日 07:03

还是觉得原生的emacs要更好用

erStern · 2019 年1 月 11 日 07:10

我日渐感觉spacemacs有些问题尾大不掉，而且不适于深入学习emacs&elisp；我看好centaur:grinning:

seagle0128 · 2019 年1 月 11 日 07:16

Centaur 还没有那么大的社区力量，我只是想分享自己的一些经验让其他人尤其是国人用起来更舒心更熟悉。多谢捧场啊

Peter-Chou · 2019 年1 月 11 日 07:16

我也觉得，spacemacs玩久了，就觉得在spacemacs框架里折腾配置有点放不开