menu
announcement

Spectrum is now read-only. Learn more about the decision in our official announcement.

styled-components

Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress!

Channels
Team

Versioning plan

August 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-components publication and we'll make it official.
Also, what do you think about going for a 1.0 after #70?

August 15, 2017 at 9:03am
> I think this is not true anymore
Whoops, just figuring out the platform ;).
Shift + enter doesn't do a newline here it seems
Anyway, I agree to your "this is not true anymore" statement, we're getting pretty close to pretty stable. This could definitely be called a beta.
like-fill
1
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!
Yep that makes sense, so a bit like a short press release
like-fill
1
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.
Show more messages