1.0.0-rc1

49 views
Skip to first unread message

ericgj

unread,
Apr 2, 2014, 11:36:51 AM4/2/14
to compo...@googlegroups.com
I see this dropped yesterday. It's great things are moving forward, but wondering why it was merged into the master branch abruptly?

I know some folks have been using Jonathan's semver stuff for awhile, and it's been discussed in various issue trackers, but I'm a bit lost even on what the new command set is, much less how the whole thing fits together under the hood. Maybe I'm the only one who feels this way and I just need to study the code. But I would have preferred some kind of release schedule, announcement, updated docs, etc. before it landed in the master branch. I would like to help with this ... as soon as I can get my head around it myself.

Component is such a great and underrated tool as it is, I would hate to see tons of new issues from people who need to upgrade node and npm, who will get frustrated because the docs are out of date, etc., and decide this component thing is broken and move on. 

Eric

Jonathan Ong

unread,
Apr 2, 2014, 7:13:29 PM4/2/14
to compo...@googlegroups.com
master is master. i hate when people develop on a "development" branch because it's hard to gauge the status of a project. 0.x is in its own branch right now, and i don't mind pushing updates to it if anyone has any issues.

the main thing for rc1 is making sure the `component install` and `component build` commands work with all the current components. if that doesn't work, then working on the other commands is futile. 

if you want to help with docs, i'm working on a readable changelog here: https://github.com/component/guide/blob/master/component-v1.md. that entire repo could use some help, but a changelog for v1 is more important for now imo. i eventually want to move ALL docs here, and make it a general discussion repo about component.

i still need to update component/component's readme, as well as point every repo to its dependencies so it's easy to understand how all the repos interact with each other. component is now split into a LOT of small libraries. the component repo actually have very little JS now. 

we also need to make component.io better and have it point to the guide. right now, going to component.io is just o.O.

Jonathan Ong

unread,
Apr 2, 2014, 7:14:33 PM4/2/14
to compo...@googlegroups.com
also, for context, segmentio contracted me last friday to specifically work on component, which is why this was all pretty quick. i want to release v1 asap so i can work on other things, which includes docs.


On Wednesday, April 2, 2014 8:36:51 AM UTC-7, ericgj wrote:

pirxpilot

unread,
Apr 2, 2014, 7:20:10 PM4/2/14
to compo...@googlegroups.com
On Wednesday, April 2, 2014 7:14:33 PM UTC-4, Jonathan Ong wrote:
also, for context, segmentio contracted me last friday to specifically work on component, which is why this was all pretty quick. i want to release v1 asap so i can work on other things, which includes docs.


Good news. Thanks segment.io ;-) And thanks for the update.
D. 

ericgj

unread,
Apr 2, 2014, 8:58:22 PM4/2/14
to compo...@googlegroups.com
Hi Jonathan,
Thanks for the link to that detailed changelog, just what I needed. It will be great to have one place for all the docs. 
And I appreciate all the work you've put to the new version, it does look fierce and I look forward to trying it out. It's always a challenge keeping docs up to date & users informed with such a large set of changes.
Eric

Reply all
Reply to author
Forward
0 new messages