That sounds good to me, and consistent with the wikipedia definition of a feature freeze. [0]
[0] https://en.wikipedia.org/wiki/Freeze_(software_engineering) --Dana Dana Walker Associate Software Engineer Red Hat <https://www.redhat.com> <https://red.ht/sig> On Mon, Nov 5, 2018 at 2:58 PM, David Davis <davidda...@redhat.com> wrote: > I was looking at the release schedule page[0] and I saw that we define > release terms like ‘beta’ and ‘release candidate’ but we don’t define what > a ‘dev freeze’ means. I’d like to add the definition of ‘dev freeze' to our > release schedule page since it sounds like there has been some confusion > around what a ‘dev freeze’ is exactly. > > The beta (as it’s currently defined on the release schedule page) is a > freeze of all features or bugs except for regressions related to the > release. Personally, I think a dev freeze should defined as a freeze of > feature (or story) work but bug fixes are permitted. > > Thoughts? I’ll leave this discussion open until next week and then update > the page unless anyone objects. > > [0] https://pulp.plan.io/projects/pulp/wiki/Release_Schedule > > David > > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev > >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
