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

Put package on melpa #4

Open
codingquark opened this issue Aug 12, 2016 · 15 comments
Open

Put package on melpa #4

codingquark opened this issue Aug 12, 2016 · 15 comments

Comments

@codingquark
Copy link

codingquark commented Aug 12, 2016

It is much much easier to have packages installed from melpa or marmalade.

@sils
Copy link
Member

sils commented Aug 12, 2016

Hey @codingquark do you know how to do this? I'm not sure if we have someone who has knowledge of that :)

@sils
Copy link
Member

sils commented Aug 12, 2016

Thanks for your interest btw.!

@codingquark
Copy link
Author

Unfortunately, I do not know. But I'll find out. :)

@lepisma
Copy link
Contributor

lepisma commented Jan 16, 2017

I too need this on some package archive. Should I put it up on melpa?

@sils
Copy link
Member

sils commented Jan 16, 2017

@lepisma that'd be awesome, can you give us access somehow so we can maintain the package?

@lepisma
Copy link
Contributor

lepisma commented Jan 16, 2017

It will just be a simple pull request to melpa (like this commit). This repository will be the go-to source. Also, a release tag will be useful.

@sils
Copy link
Member

sils commented Jan 16, 2017

Awesome! I'll just fix twoish things here then make a release tag for you within an hour or so.

@sils
Copy link
Member

sils commented Jan 16, 2017

@lepisma I made a fix and tagged latest master with 0.9.0

@lepisma
Copy link
Contributor

lepisma commented Jan 17, 2017

@sils if you merge #10 , could you also move the release tag to the commit with version in header ;; Version: 0.9.0? Thanks

@sils
Copy link
Member

sils commented Jan 17, 2017

uhm moving a tag isn't usually good practice, it's more of a bugfix release so I made https://github.com/coala/coala-emacs/releases/tag/0.9.1 after which I realized that you just declared the version as 0.9.0 in your PR. So let's declare the version as 0.9.2 and release it as 0.9.2?

@lepisma
Copy link
Contributor

lepisma commented Jan 17, 2017

Actually, there are a couple more issues before moving ahead. The checker is not working as of now.

  • There are no modes (python-mode, js-mode etc.) set for flycheck to bind this checker with
  • It doesn't add itself to the list of checker 'flycheck-checkers or provide a setup function for the same
  • Even after fixing these, there is some issue with the parsing.

I will formally file issues once I get free and pick out the problem in these couple of days. I guess tags should follow these few fixes?

@sils
Copy link
Member

sils commented Jan 17, 2017

yep we can tag anything but moving a tag is very bad practice, releases are immutable. We can do as many bugfix releases as we want, I'd restrict feature releases to be in synch with coala, i.e. we should wait til coala 0.10 (~2 weeks) if we want to add features.

@sils
Copy link
Member

sils commented Jan 17, 2017

Short: I'd first fix everything, then release 0.9.2

@sils
Copy link
Member

sils commented Feb 5, 2017

Btw. 0.10 was just released, feel free to upgrade (or not, API didn't change)

@9r0x
Copy link

9r0x commented Nov 1, 2017

I can't find it on Melpa, did you guys successfully put it there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants