search

componentjs / component

frontend package manager and build tool for modular web applications
https://github.com/componentjs/guide
MIT License
4.55k stars 306 forks source link

release of 1.0.0 #601

Closed timaschew closed 9 years ago

timaschew commented 9 years ago

@clintwood @jasonkuhrt @netpoetica @trevorgerhardt @jonathanong

what do you think to release 1.0.0?

So we can do a list what we should fix for this version, for instance I saw a note here: https://github.com/componentjs/component/blob/master/History.md#100-rc4--2014-04-04

Component 1.0.0 is now feature complete. Please help debug and open an issues you may have with this release! 1.0.0 will not be released until http://component.io is updated.

TODO before release

jonathanong commented 9 years ago

Should be fine

netpoetica commented 9 years ago

I think now is as good a time as any :-) I think I have to update the changelog where we talk about custom remotes, since we also support BitBucket now, unless there is an intention to not allow Bitbucket in 1.0?

Also I would like to merge this last pull request in, as it's pretty minimally invasive and will solve a problem that we definitely don't want to hear about in the future :)

netpoetica commented 9 years ago

Oh one thing though - I definitely think we should wait until component.io actually works, having to tell people "1.0 is released! Get it at http://www.somethingreallylong.com/somethingelsereallylong.com/" is going to look botched ;)

micky2be commented 9 years ago

Yes yes yes yes

timaschew commented 9 years ago

yep, sure, I've pinged @guille already in https://github.com/componentjs/component/issues/587#issuecomment-55507830

and I added a ToDo list in my first post

netpoetica commented 9 years ago

Merged in doc updates for custom remotes: https://github.com/componentjs/guide/pull/25

There is a pull request here that resolves components below root, but I would like one of you guys to review and merge it to make sure it's a good idea & that it shouldn't affect anything elsewhere - I added a test for it as well. Additionally, I added a warning in there that symlinking might be a better option in some situations as per conversation.

wryk commented 9 years ago

yay, component going forward ! motivation growing

timaschew commented 9 years ago

What do you think about open issues in 0.19? I think we can tag them and when 1.0.0 is ready to close the issues?

What do you think @ all?

netpoetica commented 9 years ago

Is this the only open issue in .19 atm? https://github.com/componentjs/component/issues/569

I'm going by label, not sure if maybe there is another known way of tracking issues in .19

gvilarino commented 9 years ago

I work with @slifszyc and about #569, we've already moved to v1 so I guess you can close that one.

timaschew commented 9 years ago

so seems that no one want to help out with the component.io domain

so I moved the project now to component orga back and rename it to component.github.io so that it works now with: http://component.github.io

trevorgerhardt commented 9 years ago

That's fine with me. Let's switch references from component.io to the gh-page and check that box off.

timaschew commented 9 years ago

@trevorgerhardt had you problems with the watcher?

buschtoens commented 9 years ago

Don't wanna be a downer here, but my impression was that component is kinda dead and duo is the new kid on the block.

But please correct me if I'm wrong.

netpoetica commented 9 years ago

@phvcky Duo is the new kid on the block, but

  1. More people/teams are using component than Duo in their projects simply due to how long it's been around, and it's important to continue to support them.
  2. Component still achives up to 3 times as many downloads per day from npm (note: this is probably due to it's use in a variety of deployment structures)
  3. Duo currently only supports Github as a remote whereas component supports Bitbucket as well
  4. Duo currently has > 3 times as many open issues as it's still very young

I'm looking forward to seeing Duo do great things, but, right now it's still in early growth stages, its the new kid on the block :)

buschtoens commented 9 years ago

Wow, thanks for taking time to write this elaborate answer. :)

And thanks for keeping component on life support, I guess. :D

clintwood commented 9 years ago

@timaschew, looks good to me... (and BTW great effort thanks...)

On 0.19, I think people should migrate to 1.0.0 as soon as possible. :)

On Duo, I agree with you @timaschew, @netpoetica and other comments I have seen in other threads, to me it has some nice clean ideas but is too shiny for production at this point. To be fair I haven't had the time to see how 'feature complete' it is, esp. with respect to APIs for resolvers, builders, bundlers, etc. (which I use heavily).

A fundamental issue which should be resolved since I believe it is at the root of quite a few other issues is componentjs/builder2.js#29 (@jonathanong needs your input). But that's no reason to not go 1.0.0!

trevorgerhardt commented 9 years ago

@timaschew no problems that I've ever seen, something in particular?

timaschew commented 9 years ago

because it doesn't work for me, but it's just my mac and maybe some wrong configuration and npm links ^^ but here someone else reporting an issue: https://github.com/componentjs/component/issues/585

yeah agree to fix https://github.com/componentjs/builder2.js/issues/29 and maybe this here, too: https://github.com/componentjs/component/issues/573

timaschew commented 9 years ago

so I prepared some things

my plan is to fix the issues 29 and 573 (see previous comment) and then publish component 1.0.0-rc6 and after a week or so to launch 1.0.0 :smile_cat:

we should write something about duo on an extra md file and clarify that component development will go on until duo is stable enough and stop it if it become really compatible or something like that.

but I think this note we should change:

Newcomers should use Duo instead of this implementation. Duo is more feature-complete and adds additional goodies while still supporting component.json, so check it out!

netpoetica commented 9 years ago

I agree that that line should be removed - when it is feature complete, we can reconsider, but I don't think it's worth compromising people's faith in this project by turning them to Duo right now. The development repo is awesome, nice work on that!

I think "show how to use the github token, instead of username and password" has already been fixed by showing people how to use netrc? In the docs here we point folks to the Github page which explains creating a token

timaschew commented 9 years ago

Sounds good, you're a english speaker, right? maybe you can replace or setup it in an extra file. This could be helpful: http://www.jongleberry.com/the-future-of-component.html

I think "show how to use the github token, instead of username and password" has already been fixed

Yes, that's right, I meant the remote.js repo and changelog: https://github.com/componentjs/guide/blob/master/changelogs/1.0.0.md I fixed it at these parts as well.

trevorgerhardt commented 9 years ago

https://github.com/componentjs/guide/blob/master/component/getting-started.md shows how to use a Github token instead of username/password

trevorgerhardt commented 9 years ago

Are those last two items in docs required for a release?

trevorgerhardt commented 9 years ago

The build passed after I published the latest resolver.js. Time to tag rc6?

netpoetica commented 9 years ago

@timaschew I can def. do the extra.md, no prob! I'm having trouble locating that callout that "newcomers have switched to Duo" - did you already remove it? I can also fill in this bit if you want: https://github.com/componentjs/component/tree/master#team

And then Extras.md would be in the main component repo here?

timaschew commented 9 years ago

@netpoetica yes, I removed it already, sorry, I forgot to notify you

And then Extras.md would be in the main component repo here?

I think we should make a note, that component repo has only documentation for 0.19. And everything related to 1.0.0 will be handled in the guide repo.

I can also fill in this bit if you want: https://github.com/componentjs/component/tree/master#team

Would be nice!

@trevorgerhardt I would like to fix 3 issues before we pushing rc6, with https://github.com/componentjs/builder2.js/issues/82 is almost done I updated the other two tasks in the first post

Are those last two items in docs required for a release?

Like I said, if we seperate between 0.19 and 1.0 docs by using the guide repo for 1.0.0 it's almost done. There are some articles and examples linked, which might not work with 1.0.0
These should either moved to componentjs/component wiki (which has a deprecated note) or to make the note for each article

timaschew commented 9 years ago

just published 1.0.0-rc6 :)

trevorgerhardt commented 9 years ago

woohoo!

sankargorthi commented 9 years ago

:+1:

timaschew commented 9 years ago

So, I would like to update some docs in the guide, then IMO we can release 1.0.0 :smile_cat:

netpoetica commented 9 years ago

Awesome :-) let me know if there's anything I can do to help!

timaschew commented 9 years ago

yeah would be nice if you could review these changes: e5e50 66f97

netpoetica commented 9 years ago

Working on it - got a lot of little typo/spelling/grammar fixes I will be pushing up shortly. Done: https://github.com/componentjs/guide/commit/97efd0a1c8292a90bc679fafdb76e3ad4056ae5e

timaschew commented 9 years ago

great thanks :) will publish 1.0.0 now :smile:

vendethiel commented 9 years ago

:+1:

trevorgerhardt commented 9 years ago

:+1:

wryk commented 9 years ago

wonderful ! :+1: