Skip to content
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

Plans to merge `dev` into `master`? #12418

Open
karansag opened this issue Jun 9, 2019 · 7 comments
Open

Plans to merge `dev` into `master`? #12418

karansag opened this issue Jun 9, 2019 · 7 comments

Comments

@karansag
Copy link

@karansag karansag commented Jun 9, 2019

Are there any plans to merge dev into master? There are some features I would like that were merged a while back (https://github.com/syl20bnr/spacemacs/pull/9209/commits) into dev. It would be nice to stay on master, since I'm assuming that is the most stable branch.

@tuxayo

This comment has been minimized.

Copy link

@tuxayo tuxayo commented Jun 9, 2019

Or maybe such a release model doesn't fit anymore and the devel branch should be the recommended one?

@tuxayo

This comment has been minimized.

Copy link

@tuxayo tuxayo commented Jun 9, 2019

Or could there be commits on devel that a posteriori are tagged as stable enough for the most conservative users?

@tuxayo

This comment has been minimized.

Copy link

@tuxayo tuxayo commented Jun 9, 2019

Or could there be a testing channel which would be freezed at a devel commit.
Then if not major regression are found, this commit would be tagged for release in the stable channel. And the testing channel/branch would jump to a newer commit from devel to test it's stability.
While devel would be like today.

I don't know if these ideas are relevant ^^"

@fiveNinePlusR

This comment has been minimized.

Copy link

@fiveNinePlusR fiveNinePlusR commented Jun 9, 2019

they did recently get a release

#11741

i believe releases will be more common but in general you can just backup your config/cache and update to whatever commit you'd like to use and it's usually pretty stable. might need to update your packages because spacemacs develop is usually developed for the newer packages.

@howdoicomputer

This comment has been minimized.

Copy link

@howdoicomputer howdoicomputer commented Jun 9, 2019

#11741 being closed does not constitute a release. There is no v0.300 tag or branch. The master branch hasn't seen anything other than a README update in, like, a year. The last Twitter message from the Spacemacs Twitter is from January and there doesn't seem to be any open GitHub issues for discussing cutting a new release.

The v0.300 milestone was hit but nobody ever drafted a release from it. There is a v0.301 bug fix milestone that exists despite there not being a v0.300 release - which is kind of weird. Especially since the description for the v0.301 milestone is "All issues/PRs assigned to this milestone are for regressions discovered after releasing 0.300.0 that need to be shipped out quickly."

Honestly, it's kind of hard to figure out what is going on. I saw some discussion on setting up Spacelpa and how its progress is a blocker for 0.300 but the last commit for that project was 7 months ago when various packages were added.

There is this comment by @sdwolfz saying that it's up to @syl20bnr to decide when it's okay to release. That comment was 25 days ago.

The closest thing there is right now, I think, to a v0.300 release is this branch.

Things broke for me last time I tried out develop so I usually just back port fixes into my configuration as time goes along.

@fiveNinePlusR

This comment has been minimized.

Copy link

@fiveNinePlusR fiveNinePlusR commented Jun 9, 2019

I use develop and update every so often and fix the fallout of whatever breaks if anything (last few times were fine) so it's surprising to me that they hit the .3 milestone 5 months ago but haven't done the basic release task. i'd think that you could use the .3 docs branch just fine as it's likely going to be the one that is pinned.

looks like there's about 26 commits in master that need to be merged with the docs branch. perhaps there was something in there that was not trivial to merge and they haven't had time?

@howdoicomputer

This comment has been minimized.

Copy link

@howdoicomputer howdoicomputer commented Jun 10, 2019

Yeah, no idea. I'm just trying to summarize because I was looking for a yasnippets fix that was committed to develop last year and found this issue posted at the top. It'd be great if there was a some kind of central location to get information on releases.

Or, like, if two or three people forked this project and continuously cut "good enough" releases from develop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.