Skip to content
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

Public release checklist #62

Closed
6 tasks done
jspahrsummers opened this issue Nov 13, 2014 · 21 comments
Closed
6 tasks done

Public release checklist #62

jspahrsummers opened this issue Nov 13, 2014 · 21 comments

Comments

@jspahrsummers
Copy link
Member

  • Reach out to CocoaPods folks ahead of time
  • Tease about Carthage on Twitter, prior to opening it up
  • Publish GitHub release, along with a pkg installer
  • Change repo tagline
  • Dark ship the org (make everything public, with no announcement)
  • Actually, officially announce everything
@jspahrsummers jspahrsummers added this to the Initial Release milestone Nov 13, 2014
@jspahrsummers
Copy link
Member Author

@Carthage/owners I would like to resolve #71 and #76, then I think we can dark ship the repo. What do you think?

@robrix
Copy link
Contributor

robrix commented Nov 17, 2014

👍

@mdiep
Copy link
Member

mdiep commented Nov 18, 2014

I think we should look everything over before dark shipping. You only get one first impression. ☺️

@swizzlr
Copy link
Contributor

swizzlr commented Nov 18, 2014

Would it be (im)politic to work with the maintainers of major libs (Moya, Alamofire, Quick/Nimble) to ensure it "just works" out of the box?

@tonyarnold
Copy link
Contributor

No, absolutely not. I say go for it.

@paulyoung
Copy link
Contributor

❤️

@jspahrsummers
Copy link
Member Author

I think we should look everything over before dark shipping.

@mdiep What does it mean to “look everything over?” Fix all the bugs in the milestone?

I would certainly like to dark ship before we have everything tightened up. I'm tired of working behind closed doors.

Would it be (im)politic to work with the maintainers of major libs (Moya, Alamofire, Quick/Nimble) to ensure it "just works" out of the box?

@swizzlr I like this idea, but I think it should wait until we've publicized the repo. We'll probably have to, in order to submit the appropriate PRs anyways.

@swizzlr
Copy link
Contributor

swizzlr commented Nov 18, 2014

Since I do like this idea I will privately try to prepare some patches, if necessary, that I can open as PRs when you release.

I would certainly like to dark ship before we have everything tightened up. I'm tired of working behind closed doors.

Yolo. (for real).

@jspahrsummers
Copy link
Member Author

@swizzlr 🤘

@jspahrsummers jspahrsummers changed the title Initial release checklist Public release checklist Nov 18, 2014
@jspahrsummers
Copy link
Member Author

Released version 0.1 to get a feel for the process, and demonstrate the new installer.

We can increase the version number once the milestone is actually complete and we're 100% ready to be vocal about Carthage to the world.

@ashfurrow
Copy link

@swizzlr I'm touched that you consider Moya a major repo.

@jspahrsummers
Copy link
Member Author

@Carthage/owners I would like to make this repo public tomorrow. Speak now or forever hold your peace. :godmode:

@alanjrogers
Copy link
Contributor

👍

@swizzlr
Copy link
Contributor

swizzlr commented Nov 19, 2014

@ashfurrow Way Of The Future.


Important Repos For The Modern Era:

ReactiveCocoa/swift-development
Moya
Alamofire
AFNetworking
Argo/Mantle (pick your poison)

@jspahrsummers
Copy link
Member Author

@Carthage/carthage All of the outstanding issues in the milestone have been fixed, and tagged in 0.2. How does everyone feel about starting to announce the project?

@paulyoung
Copy link
Contributor

Make it so!

@NachoSoto
Copy link
Contributor

🎉

@joshvera
Copy link
Contributor

:shipit:

@mdiep
Copy link
Member

mdiep commented Nov 19, 2014

🚢

@jspahrsummers
Copy link
Member Author

@robrix
Copy link
Contributor

robrix commented Nov 19, 2014

👍

natanrolnik pushed a commit to natanrolnik/Carthage that referenced this issue Feb 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants