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

Write a blogpost for 3.0.0 #4042

Closed
2 tasks done
Murderlon opened this issue Aug 24, 2022 · 7 comments · Fixed by #4046
Closed
2 tasks done

Write a blogpost for 3.0.0 #4042

Murderlon opened this issue Aug 24, 2022 · 7 comments · Fixed by #4046

Comments

@Murderlon
Copy link
Member

Murderlon commented Aug 24, 2022

Initial checklist

  • I understand this is a feature request and questions should be posted in the Community Forum
  • I searched issues and couldn’t find anything (or linked relevant results below)

Problem

No release blog post

Solution

Write a release blog post.

Highlights, in order of importance:

  1. ESM
  2. Robodog is deprecated
  3. New Companion major
    1. @mifi list the most important ones please
  4. New plugin: remote sources
  5. Webcam supports native camera
  6. Stable aws-s3-multipart
  7. Stable compressor
  8. Updated examples
  9. Smaller changes
    1. Support React 18
    2. Angular 14 (maintenance support for older versions, same as Robodog)
    3. Vue 3 support, @uppy/vue turned 1.0.0
    4. tus-js-client 3.0.0
    5. ?
    6. Lots of bug fixes (would be great if we could somehow aggregate the number)

We would also need artwork, similar to https://uppy.io/blog/2021/08/2.0/, for the blog post and socials. I think @nqst can help with this.

@nqst
Copy link
Contributor

nqst commented Aug 25, 2022

Do you have any ideas for the subtitle (we used "Smaller, faster & more awesome" for 2.0)? Or would just "Uppy 3.0" be sufficient?

@Murderlon
Copy link
Member Author

Murderlon commented Aug 25, 2022

I think a subtitle would be nice indeed. I think we want to focus on that we took a step into the future with ESM, we have less integration code now with the remote sources preset, and things have become (even more) stable.

Initial ideas:

  • "Future proof, easy in use, stable"
  • "Passionately future proofed, devotedly stable, loyally familiar"

@arturi
Copy link
Contributor

arturi commented Aug 25, 2022

I'd go with a variation of number 1 :)

@Murderlon
Copy link
Member Author

I'd go with a variation of number 1 :)

I don't like that "stable" implies that it wasn't before, so it needs some slight adjusting.

@nqst
Copy link
Contributor

nqst commented Aug 25, 2022

Haha, I really liked the second option :D 🐶

Thanks, folks! Think now I have enough to get started.

@mifi
Copy link
Contributor

mifi commented Aug 25, 2022

For Companion, there's not that many exciting news for the end user.

  • Streaming upload can now be enabled in Companion with Tus. This gives greatly improved upload speeds when using Providers and allows uploading potentially hundreds of gigabytes without needing a large server storage. @uppy/companion: upgrade tus-js-client to v3 #3851
  • Companion now has a server-side event emitter that can be used to detect when uploads start, finish and fail, without having to depend on the client (works after user has closed their browser) How to track the completion of upload to s3 via companion  #3435
  • We did rewrite to more async/await and grossly simplified our Provider code in Companion: rewrite request and purest to got #3953, but it's not that exciting because the interface stays the same. Although I think it makes it much easier for people to write their own providers now.
  • Maybe we can say that our dependencies are more up-to-date now and using less old packages with security vulnerabilities?

@arturi
Copy link
Contributor

arturi commented Aug 26, 2022

@mifi this is for developers, so the more detailed, the better actually :) Def need to mention the Request rewrite. And more details on streaming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants