3 years and 1.0 pre release #1213
Conversation
|
@shcheklein and @jorgeorpinel could you please help me with the publishing?
|
Co-authored-by: Restyled.io <[email protected]>
|
|
||
| We are sharing our learnings from this journey and how they affected the new | ||
| DVC 1.0 release. | ||
| picture: 2020-05-04/5k_stars.png |
There was a problem hiding this comment.
we need a 2x size image to make it sharp
Co-authored-by: Restyled.io <[email protected]>
| `dvc pull \ push \ status -c \ gc -c`. Now, based on the amount of data, DVC can | ||
| choose an optimal data remote traversing strategy. | ||
|
|
||
| [Wini-indexes](https://github.com/iterative/dvc/issues/2147) were introduced to |
There was a problem hiding this comment.
better to put link to @pmrowla report
There was a problem hiding this comment.
Provided the link and the plot. Looks very solid 😎
| $ open logs.html | ||
| ``` | ||
|
|
||
|  |
There was a problem hiding this comment.
can we make them a bit bigger?
| @@ -0,0 +1,198 @@ | |||
| --- | |||
| title: DVC 3 Years Anniversary and 1.0 Pre-release | |||
There was a problem hiding this comment.
can we omit Anniversary - to make it fit into a single line
There was a problem hiding this comment.
Maybe "DVC Year 3 and 1.0 Pre-release"
There was a problem hiding this comment.
DVC 3 Years and 1.0 Pre-release ?
There was a problem hiding this comment.
DVC 3 Years 🎉 and 1.0 Pre-release 🚀 ?
There was a problem hiding this comment.
What about 3 years of DVC and 1.0 Pre-release?
| 🚀 DVC 1.0 pre-release is ready and ⭐ 5000 GitHub starts. | ||
|
|
||
| descriptionLong: | | ||
| Today, we’ve got three big things to announce. |
There was a problem hiding this comment.
Today, we've got three big announcements.
|
|
||
| ⭐ DVC has reached 5K GitHub starts (coincidently on the same day) | ||
|
|
||
| We are sharing our learnings from this journey and how they affected the new |
There was a problem hiding this comment.
The last sentence is a bit awkward. Maybe, We'll share what we've learned from our journey and how DVC is growing.
There was a problem hiding this comment.
I'm trying to make a connection between the learning and the features we release. How about We'll share what we've learned from our journey, how it helped for the release and how DVC is growing.?
| page to not to confuse users. | ||
| [The first DVC discussion on Reddit](https://www.reddit.com/r/Python/comments/698ian/dvc_data_scientists_collaboration_and_iterative/). | ||
| A few days later it was | ||
| [republished on other sources](https://www.kdnuggets.com/2017/05/data-version-control-iterative-machine-learning.html) |
There was a problem hiding this comment.
I don't think showing these old posts makes a very strong point. I would condense it a lot:
Three years ago on **May 4th, 2017**, I published the [first blog post about DVC](https://www.kdnuggets.com/2017/05/data-version-control-iterative-machine-learning.html). Until that point, DVC was a private project between myself and two others, my cofounder Ivan and our collaborator, Ruslan. Today, things look very different.
or some variant of this
| I can confidently say that DVC wouldn't have been possible without a lot of help | ||
| from our community. Thank you to everyone who has supported us: | ||
|
|
||
| **DVC core team.** The core team of the project takes the majority of the |
There was a problem hiding this comment.
I think take a bigger scope- mention that the team is now 12 full-time people or however large we technically are (even though they're not all "core DVC engineering"; this is more about Iterative).
|
|
||
| **DVC core team.** The core team of the project takes the majority of the | ||
| development activities, constantly brings new ideas, documents the product and | ||
| always on the first line of user's support. Many users knows that great user |
There was a problem hiding this comment.
Grammar rewrite:
The DVC team has been the force driving our project's evolution- we've grown from 2 to 12 full-time engineers, developers, and data scientists. We often get feedback about how fast our team answers user questions- we've been told our user support is one of DVC's "killer features". It's all thanks to this amazing team.
| on May 4th, 2017. Coincidently, today, in the 3rd year anniversary we have | ||
| reached 5000 starts: | ||
|
|
||
|  |
There was a problem hiding this comment.
I think you should use my owl gif https://gph.is/g/Z5BgyGD
There was a problem hiding this comment.
@andronovhopf do you have the same gif without 5K starts on the top by any chance? :)
There was a problem hiding this comment.
It looks great but does not work as the front image. The issue is the resolution I guess or gif might not be supported as the front image. Keeping the old one for now. And looking for other options.
| piece of your help is highly appreciated and will bring huge benefits to the | ||
| entire ecosystem of data and ML projects. | ||
|
|
||
| Stay healthy and safe over in your neck of the woods and be in touch on |
There was a problem hiding this comment.
Stay healthy and safe, wherever you are in the world. And be in touch on our Twitter and Discord channel!
|
… On Sun, May 3, 2020 at 7:11 PM Dmitry Petrov ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In content/blog/2020-05-04-dvc-3-years-and-1-0-release.md
<#1213 (comment)>:
> +This feature was actually released in the last DVC 0.93 version (see
+[params docs](https://dvc.org/doc/command-reference/params). However, it is an
+important step to support configuration files and ML experiments in a more
+holistic way.
+
+I hope our the most active users will find time to check the DVC pre release
+version and provide their feeback. The installation instruction is
+[on our website](https://dvc.org/doc/install/pre-release).
+
+## 5000 GitHub stars
+
+Activity on our GitHub page has grown organically since the DVC repo went public
+on May 4th, 2017. Coincidently, today, in the 3rd year anniversary we have
+reached 5000 starts:
+
+
@andronovhopf <https://github.com/andronovhopf> do you have the same gif
without 5K starts on the top?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHCXB5FTWCZQYU6MEAKYR63RPYP6ZANCNFSM4MYCDSDQ>
.
|
|
That’ll work!
… On May 3, 2020, at 11:11 PM, Dmitry Petrov ***@***.***> wrote:
@dmpetrov commented on this pull request.
In content/blog/2020-05-04-dvc-3-years-and-1-0-release.md:
> +title: DVC 3 Years Anniversary and 1.0 Pre-release
+date: 2020-05-04
+description: |
+ Today, we’ve got three big things to announce: 🎉 3rd-year anniversary of DVC,
+ 🚀 DVC 1.0 pre-release is ready and ⭐ 5000 GitHub starts.
+
+descriptionLong: |
+ Today, we’ve got three big things to announce.
+
+ 🎉 3rd-year anniversary of DVC
+
+ 🚀 DVC 1.0 pre-release is ready
+
+ ⭐ DVC has reached 5K GitHub starts (coincidently on the same day)
+
+ We are sharing our learnings from this journey and how they affected the new
I'm trying to make a connection between the learning and the features we release. How about We'll share what we've learned from our journey, how it helped for the release and how DVC is growing.?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
|
||
| All these contributions, big and small, have a collective impact on DVC's | ||
| development. I'm happy (and a bit nervous) to announce that a pre-release of a | ||
| brand new DVC 1.0 is ready for public beta testing. |
There was a problem hiding this comment.
| brand new DVC 1.0 is ready for public beta testing. | |
| brand new DVC 1.0 is ready for public alpha testing. |
There was a problem hiding this comment.
"Alpha testing is carried out in a lab environment and usually, the testers are internal employees of the organization" https://www.guru99.com/alpha-beta-testing-demystified.html
There was a problem hiding this comment.
Here's a post-merge review with things I plan to improve in a coming regular updates if you agree @dmpetrov but please note a couple questions in there:
| We redesigned the DVC-metafile format to make saved pipelines more interpretable | ||
| and editable. Pipeline stages are now saved in a single metafile, with all | ||
| stages stored together instead of in separate files. |
There was a problem hiding this comment.
redesigned the DVC-metafile format
But regular .dvc files will continue to exist independently for some commands right? Like dvc add/import @dmpetrov
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
* blog: fix typos in 2.0 pre-release post * blog: address pending review items from original my PR review per #1213 (review) * blog: avoid scalar and continuous terms (metrics) in 1.0 post
Pre-release and anniversary blog post.