-
-
Notifications
You must be signed in to change notification settings - Fork 929
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
Roadmap for 0.1.0 #15
Comments
I think we should
|
Thank you. I understood! |
That said I will reopen this one so we make things accessible for everyone. |
That's better:D |
Shall I create a |
Likewise, I can port over [#14] to |
I think roadmap should be just opened issue, maybe using github milestone. |
Maybe we can close #1 and open corresponding issue (then using github assignement to say "I am on it" with a wip label ?) (I will import labels tomorrow morning) |
Do you mean create an issue for each of the rules within the list? There's a lot, about a 100 I think. Or did you mean something else? |
You r right.
We can also just update the existing issue again :) |
Oh, I didn't realise I could do that now. Neat :) Updating the existing issue makes the most sense to me:
How does that sound? |
lgtm ! |
Great. |
I've added the checklist to #1. I figured it doesn't formalise things too much as the on-going discussion is laid out directly below it. What is left to do on this issue before we can get the likes of @tgfjt involved? Wait for @davidtheclark's PR 33 to be merged (with the new testing infrastructure), and then do a release? |
@MoOx Now that 4 rules are done. Is this a good time to cut a new release? Quick other question about workflow... one of the rule names is wrong in |
Seems to me that typos like that you should feel free to just fix. |
Done :) |
I started a new (short) contract yesterday, so I won't be able to do much on stylelint this week. Lets get |
I've tried on some situations. It totally seems to be great! |
Great to hear! I think we're looking good for a release next week :) |
I'd also like to user "stylelint-config-suitcss"! 👍 |
I'm back. I don't see any issues that need fixing, so maybe it's time to release 0.1.0 and ask some people to try it out? I don't know if I feel good about trying to get much attention until #133 is resolved ... but the more early adopters we can get to try it the better. |
Hey, I've been watching this repo for approximately the last month, hope you've all enjoyed your recent well deserved time off, I know I have had a tidier inbox ;) Anyways, I just thought I'd add a comment here to saying that I think what your doing is awesome, there's been quite a lot of said awesome flow throw my inbox this past month. I plan on and have already begun some initial tests to add this to the WordPress project, so I'm really looking forward to the 0.1.0 release. (And yeah #133 would be nice) |
@davidtheclark Welcome back! I hope you had a nice week :)
Agreed. A quiet release makes sense to me. We can also add a little note to the top of the README, perhaps replacing the current "See the 0.1.0 roadmap issue for details of our progress towards the first release", which reads "Note: see issue #133 for details of our progress towards more accurate line numbers". At least that way early adopters' expectations will be set when they come to use
I reckon so :) If I make the README file amends, are you able to run through the release process? @ntwb Glad you're finding the linter useful :) Is it the Wordpress CSS Coding Standards that you'll be checking against? I had a quick look though it and I think the linter will check most of it. Let us know if there's something in the standards that's missing though and we'll look into ways to include it in the linter. |
Jeddy3 wrote:
Yes, that's it :)
Agreed, I think most things are good to go, and for sure I'll let you know if we hit any hurdles :) |
Sounds good @jeddy3. I could make the release tonight. |
ntwb wrote:
Good stuff. Those standards seem like a great candidate for a shareable config. Give me a shout if you want me to setup a But if you're happy working with your own local config, well that's totally groovy too :) |
Jeddy3 wrote:
This sounds like a great idea, and for sure will help out the WordPress sub-projects I know that will follow suit and also begin using stylelint. The one thing I want to just note is that getting this into WordPress Core is not guaranteed, I'm one of the build tools maintainers for WordPress so things look promising, just wanted to say that nothing is a sure thing is all ;) |
I just released 0.1.0. As a trial, I integrated into a project I've been working on -- and everything went smoothly. Let me know if the same doesn't happen for you. |
🎉 |
💥 |
👍 gooood job @stylelint/owners |
@davidtheclark @jeddy3 is the CHANGELOG up to date ? I will tweet about this release. |
I will try to check the CHANGELOG. I did make a release, but didn't add annotation so it is not good reading :) I can manually fix that for this release and then we can try the script next time. Do you normally include it in a repo or just use it from your computer? |
This command can be executed after the tag creation, so you might be able to use it even now (if you rename v0.1.0 to 0.1.0 or if you adjust the script). I use npmpublish + npmrelease which are 2 commands (on to test/publish/tag and the other to transform the tag to a github release). I use them from my computer (dotfiles) but maybe I can push those to npm or something. Maybe just the 2, cause my npmpublish command is pretty simple. I already see some alternative that generate changelog+github release from commits but I don't find it's accurate most of the time (some commits, like refactoring or pure doc have nothing to do in changelog for me). |
@davidtheclark fyi, I finally published my npmpublish and npmrelease command. get npmpub(lish) && github-release-from-changelog as dev deps $ npm i -D npmpub github-release-from-changelog add a script this way (in package.json "scripts" section) {
"scripts": {
"release": "npmpublish && github-release-from-changelog"
}
} So now you can prepare changelog+bump package by hand and then just do 2cents advice try this on a small repo first, just in case (it's the same code, but your never know, it's still fresh). I used those packages themselves to publish and release themselves as a test ^^ |
Looks groovy thanks. I'm going to flag this up in another issue as I'm afraid it'll get missed here. |
Thanks @MoOx! |
Hello!
Do you have any Roadmap or something? is it #1?
I'm interested in preparation and implementing of rules.
I'm looking forward to try & counting on stylelint.:smile:
The text was updated successfully, but these errors were encountered: