<div dir="ltr"><div>tl;dr we follow <a href="http://semver.org">semver.org</a> and I agree with your reasoning, so I'm convinced 1.0 would be fine. While I'm not in favor of the change, I'm ready to disagree and commit.<br></div><div><br></div><div>In the interests of sharing perspectives, here's mine. The issue with <a href="http://semver.org">semver.org</a> is that it's exclusively focused on change management, and it ignores what I perceive as a cultural association with > 1.0 software to mean "broadly tested and low risk". Is pulp_file at a point where backwards compatibility is a primary concern and prohibited yes. Do the developers of pulp_file recommend it to be run in production, yes. As a user, is it a low risk software due to many folks having already deployed it in production, no. In fact pulp_file is maybe in the high to medium risk category based on the number of folks who are actually running it in production.</div><div><br></div><div>Having said all that, I'm ready to support your proposal on the semver basis. Your reasoning is sound. Thank you for writing your thoughts here and your effort to make it great.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 22, 2020 at 11:32 AM David Davis <<a href="mailto:daviddavis@redhat.com">daviddavis@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I want to expound on my own reasoning behind why pulp_file should be bumped to 1.0 because I realize my original email was probably too brief and I apologize for that.<div><br></div><div>The thing that I would refer to is <a href="http://semver.org" target="_blank">semver.org</a> which we've used as a guide for versioning. <a href="http://semver.org" target="_blank">semver.org</a> defines a 0.Y release as:</div><div><br></div><div> Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.</div><div><br></div><div>Moreover, <a href="http://semver.org" target="_blank">semver.org</a> has this question/answer:</div><div><br></div><div> How do I know when to release 1.0.0?<br> </div><div> If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.<br><br></div><div>I think we meet both of these criteria. I expect that Pulp users are probably using pulp_file in production already. In terms of its API, we've had only two small features in the last couple releases of pulp_file since 0.1.0[0] and no major changes to the public API (there was the rename of one field). I don't foresee any major changes to the public api anytime soon. There's not a roadmap for new features either and certainly nothing I see that could cause major changes to pulp_file's API.<br></div><div><br></div><div>I think that in this context it makes sense to bump it to 1.0 to communicate to our users that the pulp_file API is stable enough to use in production.</div><div><br></div><div>Thoughts?</div><div><br></div><div>[0] <a href="https://github.com/pulp/pulp_file/blob/master/CHANGES.rst" target="_blank">https://github.com/pulp/pulp_file/blob/master/CHANGES.rst</a><br><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>David</div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 22, 2020 at 10:59 AM David Davis <<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I feel differently especially when considering that most other Pulp plugins are at > 1.0. Can you explain why you think pulp_file shouldn't be at 1.0?<br clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>David</div></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 22, 2020 at 10:57 AM Brian Bouterse <<a href="mailto:bmbouter@redhat.com" target="_blank">bmbouter@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>I've seen software live in the < 1.0 area for a long time and graduate when it's in broad, production use. That's a difficult thing to assess accurately, but to me, pulp_file hasn't reached that point.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 21, 2020 at 2:20 PM David Davis <<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">With the next release of pulp_file, I'd propose we bump the version to 1.0. The pulp_file plugin has reached a level of maturity and stability that I think it could be considered production-ready. I've opened a PR to bump the version to 1.0.0:<div><br></div><div><a href="https://github.com/pulp/pulp_file/pull/380" target="_blank">https://github.com/pulp/pulp_file/pull/380</a></div><div><br></div><div>Feedback welcome. I'll set a deadline of April 27, 2020.<br clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>David</div></div></div></div></div></div></div></div></div></div> _______________________________________________<br> Pulp-dev mailing list<br> <a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br> </blockquote></div> </blockquote></div> </blockquote></div> </blockquote></div>