Stable release

Question

Stable release

ddeboer opened this issue 10 years ago · 10 comments

What needs to be done before a stable release? If we decide that we need some tests (#4) we can do so after the stable release, I guess.

dbu commented 9 years ago

see #18

Answer 1 · 2016-01-28T07:56:47.000Z

I agree, I can't see any blocker.

Readme/Contributing guide/Code of conduct needs update.

Answer 2 · 2016-08-23T06:55:31.000Z

do we have something to update those files automatically? or should i just copy them from the current skeleton?

i guess we should decide on #3 before tagging stable?

Answer 3 · 2016-08-23T07:15:43.000Z

We (Mark) copy them as far as I know.

Answer 4 · 2017-01-20T16:04:25.000Z

Do we have anything that keeps us from tagging 1.0.0?

Answer 5 · 2017-01-20T16:08:20.000Z

unless we feel we need to BC break for #3 and its very simple, i would say lets tag. maybe lets just tag anyways and if somebody works on #3 and it needs breaking changes, we can always do a 2.0 if its worth it

Answer 6 · 2017-01-25T21:34:57.000Z

A stable tag would be nice :)

Answer 7 · 2017-03-10T13:44:34.000Z

@dbu please "tag anyway". I'm developing a library and won't be able to run my tests with a version 1 of php-http/discovery because of this. It does not feel safe…

Answer 8 · 2017-03-10T14:23:41.000Z

Love your responsiveness!

Answer 9 · 2017-03-10T14:36:28.000Z

Follow-up doc PR : php-http/documentation#181