Time for a 3.1 release!

[xzyfer]

It's about a month since our previous release and we've already added 98 commits to master since this release. I'm keen to keep the momentum rolling! We have a lot of good stuff on master as one can see by looking at the closed issues since then.

I'm opening this issue mainly because of @mgreter's incredible API updates. I want downstream libraries to be aware of the impending release and API changes to reduce lag time in implementation.

Open Pull Requests

• Improve custom importer to pass parent import context
• Add tap reporter to test targets
• Add tap output reporter to spec runner
• Improve color token operations
• Implement emitting utf8 charset when seen in output
• Sassc: Use new functional libsass C API

Most need only review or further feedback!

Open Tasks

• update C-API wiki for new API
• update documentation for building libsass
• check wiki for obsolete stuff
• update Readme.md for new API
• Gather changes for release notes
• Add appveyor badge to Readme.md

[mgreter]

I would like to get #691 merged before the next release, since it contains some minor API updates. It already works, but it should be implemented a bit cleaner IMO. BTW. the old API is still in place and should not stop working (if no Sass_Values are used). I also have a branch around for sassc to update to the new API. Beside that there's nothing on my side against 3.0.3 👍

[xzyfer]

I think those things are worth waiting for. I've added a checklist to the issue to track progress.

[mgreter]

OK, I guess/hope I can get my open things sorted out till this weekend!

[xzyfer]

No need to rush :)

I think we're at a point where the remaining issues are significant chucks of work so future releases may be further spread out. It'd be good to get out some of the good stuff on master in the mean time is all.

[HamptonMakes]

We should definitely do a pre-release.

On Tue, Dec 9, 2014 at 5:03 AM, Michael Mifsud notifications@github.com
wrote:

It's about a month since out previous release. I'm keen to keep the momentum rolling! We have a lot of good stuff on master which I've tried to summaries in https://github.com/sass/libsass/issues?q=milestone%3A3.0.3+is%3Aclosed.
I'm opening this issue mainly because of @mgreter's incredible API updates. I want downstream libraries to be aware of the impending release and API changes to reduce lag time in implementation.

/cc @hcatlin @mgreter @am11

Reply to this email directly or view it on GitHub:
#697

[drewwells]

what wiki updates are you looking for? https://github.com/sass/libsass/wiki/API-Documentation and https://github.com/sass/libsass/wiki/Custom-Functions-internal

[xzyfer]

@drewwells I'm not 100% sure. It was a reference to the still changing C API that @mgreter is working on. Just a reminder to reflect any upcoming changes in the docs.

[xzyfer]

How are you feeling about a pre-release @mgreter ?

[am11]

node-sass can use a corresponding subsequent (pre)release before the holidays. :)