Show previous messages
Versioning planAugust 15, 2017 at 8:31am
The README currently says
NOTE: This is currently in alpha. While unit-tested, it doesn't yet have a lot of real world project exposure, so there'll be some edge cases we haven't covered. Please try it out and submit bug reports!
I think this is not true anymore with the recent work by and and all the bugs that've been fixed.
Let's make 0.3.0 the first "beta" version and announce it as such? I'd love to publish an article on Medium about the recent improvements we've made, does one of you want to kick that off? If you just start writing a draft and send that over to me I can add you to the
styled-componentspublication and we'll make it official.
Also, what do you think about going for a
Show more messages
August 15, 2017 at 9:13am
August 15, 2017 at 9:13am
I've never written a Medium article but there's a first for everything, I think it could be quite fun. So yeah I think I could try working on a draft for that! What specific things were you thinking of including in the article? Since I joined the team we've done a lot of bug fixes, the most "real" changes I've done are probably giving the fixIndentation function a makeover in #77 and the interleave function a makeover in #63. Would we want to discuss #70 already or is that for another Medium article when releasing 1.0?
And yeah I had actually also been thinking about going for a 1.0 after #70, simultaneously we might also just wanna sweep up the last few small bug issues that #70 doesn't fix but then I'd be super up for a 1.0
Let's do one for 0.3 and then another big one for 1.0. The 0.3 one should just be a simple "This is what we've fixed, it's now a beta, we're working hard on a 1.0, if you've tried it before but it didn't work try it now, follow the progress and contribute here" I think?
Just starting writing an article on Medium and there should be a button to share a draft so I can comment on it and add it to the styled-components publication!
One thing that might be a bit confusing is that while we're considering the current releases alphas, they're not tagged as such on npm.
Likewise, when releasing a beta I'd expect it to be accompanied by the appropriate tag on npm. Which makes npm not install it unless you specify the exact tag. Maybe just calling it the first stable release would be more clear? I don't know, might be nitpicking, but I usually assume a beta to be the preliminary release of a new major version. And then once we get to a stable point release a release candidate, etc. But again, that might be nitpicking.
Also, let me know if you need help reviewing a draft, I'd be happy to.
Also, I might be mistaken about the above, so please correct me if I'm wrong.
I don't think so in this case. I agree if we'd put out an actual stable version before that that would be under the @latest tag (i.e. the one that gets installed) and people can opt-in to the beta by using npm i [email protected]
In our case though we've only had an alpha version so far and we're now upgrading that to be called a beta version
There is no stable version though so that's what you get when you install
It's mostly just a marketing thing 😉
Yeah I think I agree that the understanding you express of alpha and beta @ismay are only for 1.0+, that's at least my understanding :)
I'm just writing the last characters on a rough draft and then I'll share it here1
there we go
haven't looked much over it so go easy on me ;)1
but yeah I don't feel any strong ownership so it's up to you whether you want to give me suggestions and have me change it or just take it, edit it and publish it, no consent needed.
I've added you as a Writer to the styled-components publication on Medium (both of you), so you should be able to submit that article to the publication somehow?
Then I should be able to edit and publish it I think
Article looks great! I'll try and create some sort of feature image for it so it shows up more nicely on social media