release 1.6 ?

[lukeapage]

Hi,

@seven-phases-max / anyone else

It seems like a good time to do a release.. anything else in the pipeline soon?

anyone think we should do a beta first? apart from people trying out new features, I'm not sure many people use it..

[jonschlinkert]

👍, in terms of beta you're definitely the best judge of that. you see the patterns before/after each release so I'm good with whatever you decide

[matthew-dean]

I think we had discussed a procedure of releasing betas first, as there is some software out there that grabs the "latest" from our Github repo and drops it into compiling systems. Like Jon, I don't have a clear sense what is different between 1.5.1 and 1.6. Are there many new features?

[seven-phases-max]

I guess it's a good time. At least I have nothing to PR in this year anymore :)
And for the beta I share @lukeapage's suspicions of "I'm not sure many people use it..".

@matthew-dean

I don't have a clear sense what is different between 1.5.1 and 1.6. Are there many new features?

changelog?

[seven-phases-max]

P.S. Ah, I almost forgot. There's one "hanging" pull-request that could be possibly added to 1.6: #1737. But in fact it's so very minor that I'm not quite sure when or if it should go in. At first it may be thought as an issue fix but actually I doubt there's any code out there that suffers from that "issue" so no reason to rush this into 1.6. On the other hand (counting it as a "breaking change"), for the same "barely seen in real projects" matter it hardly breaks anything so no reason to postpone it too (i.e. it can be counted just as "generic consistency patch"). Unless I'm missing something else that can be possibly wrong with this PR changes.

[matthew-dean]

Hey! We have a changelog! Radness.

[jonschlinkert]

Hey! We have a changelog! Radness.

Yeah, it's pretty new. I think it was added in v1.first commit

[matthew-dean]

:P lol, I forgot about it. To be fair, the history only takes it back to v1.3.1. BURN SCHLINKERT haha.

[jonschlinkert]

yeah I was just kidding, I didn't check. But now that I have, just to fair, it's been there for 2 years ;-)

[matthew-dean]

My experience with changelogs is that after a release you go, "Huh, I should probably update that Changelog." I didn't expect @lukeapage to be so on top of it as to keep it updated BEFORE a release. I mean, I knew he was awesome but I didn't expect him to be THAT awesome.

[jonschlinkert]

@lukeapage seems to be on top of just about everything

[matthew-dean]

Indeed. @lukeapage are we releasing 1.6 then?

[lukeapage]

Yes.. as soon as I get some time.

[lukeapage]

done, just need to update the site