Release this year?

[Chris Burroughs]

There have been ~530 commits to master since the 1.3.0 release in 2014.
That feels like a big old chunk of work. Is there a rough roadmap (in
terms of either time or features) for the next release?

[Will Richard]

Hi Chris,

Yeah, you're right that we're long overdue for a release.  The code is ready to be released, but we need to write a lot of documentation for the changes we've made.  I'll make sure we focus some time on that, and get things cleaned up to cut a release.

Just so you know, we're likely to go right to 2.0.0, because we've made some backwards incompatible configuration changes, and we want to start following symantic versioning.

Sorry for the delay on this - like I said, I'll make sure we start working on getting those docs in shape.

[Michael Schenck]

Any chance of having a public community (with governance, commit privileges, etc) so others can help define a roadmap, release cycle, etc?

--
You received this message because you are subscribed to the Google Groups "Collins" group.
To unsubscribe from this group and stop receiving emails from it, send an email to collins-sm+...@googlegroups.com.
To post to this group, send email to colli...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/collins-sm/39f981ab-ebb7-459c-958f-d4ee95e959c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Github • LinkedIn • Tumblr • Twitter

[Will Richard]

That's a good idea.  I'll ask around here and try to make it happen - I don't think it's something we've done before, so I may need to ask around and figure out how to make it happen.

On Tuesday, February 2, 2016 at 4:42:06 PM UTC-5, Michael Schenck wrote:

Any chance of having a public community (with governance, commit privileges, etc) so others can help define a roadmap, release cycle, etc?

On Monday, February 1, 2016, Will Richard <wi...@tumblr.com> wrote:

Hi Chris,

Yeah, you're right that we're long overdue for a release.  The code is ready to be released, but we need to write a lot of documentation for the changes we've made.  I'll make sure we focus some time on that, and get things cleaned up to cut a release.

Just so you know, we're likely to go right to 2.0.0, because we've made some backwards incompatible configuration changes, and we want to start following symantic versioning.

Sorry for the delay on this - like I said, I'll make sure we start working on getting those docs in shape.

On Monday, February 1, 2016 at 4:12:47 PM UTC-5, cburroughs wrote:

There have been ~530 commits to master since the 1.3.0 release in 2014.
  That feels like a big old chunk of work.  Is there a rough roadmap (in
terms of either time or features) for the next release?

--
You received this message because you are subscribed to the Google Groups "Collins" group.

To unsubscribe from this group and stop receiving emails from it, send an email to collins-sm+unsubscribe@googlegroups.com.

To post to this group, send email to colli...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/collins-sm/39f981ab-ebb7-459c-958f-d4ee95e959c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Corwin Brown]

Any update on a release?

[Will Richard]

Hi Corwin,

Making progress - we're about half way done with the docs that we need to write before we feel good about cutting a release - I'll make sure we double down on working on it!

-William Richard

--

You received this message because you are subscribed to the Google Groups "Collins" group.

To unsubscribe from this group and stop receiving emails from it, send an email to collins-sm+...@googlegroups.com.

To post to this group, send email to colli...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/collins-sm/c1de5f53-51a6-45e5-b6c9-84ba6f2bccae%40googlegroups.com.

[Patrick Lundquist]

Hi Will, 

Any update on the release? Or any chance we could get a documentation preview?

We're looking to either try deploying Collins or start rolling our own system this month. 

Cheers,

Patrick

[Will Richard]

Hi Patrick,

The docs currently on http://tumblr.github.io/collins/index.html are for the master branch, which we consider stable and are using in production.

We don't have a solid date on the release, but we're working on it.

Please give collins a try and let me know if you need help getting going!

-William Richard

To view this discussion on the web visit https://groups.google.com/d/msgid/collins-sm/2696e965-0695-42c9-a1cb-9f55b62163fe%40googlegroups.com.

[Alan Sparks]

On Tuesday, June 14, 2016 at 1:00:09 PM UTC-6, Will Richard wrote:

We don't have a solid date on the release, but we're working on it.

Any progress to report, does an update date seem more concrete yet?

[Johannes Ziemke]

Hi everyone,

that sounds like a really good idea!

I'm a collins user and Prometheus maintainer. With Prometheus we joined the CNCF recently (although I wasn't much involved in the process). If you're interested, can ask around if collins would be a fit as well and how that would work etc.

[Will Richard]

I'm happy to announce that we did manage to get another release done this year! And we're going to make sure we are releasing more frequently, with smaller changes, to avoid these sorts of giant changesets all at once.

https://github.com/tumblr/collins/releases/tag/v2.0.0

I'll be sending another message to the group soon with the details of the announcement.