Brenden Soares

I've pushed this back to v0.15. This may not be a straight forward task and will likely need a cross-platform signaling solution (as mentioned in other issues involving SIGINT on...

Hi guys. This is assigned to v0.14 and the next release is v0.13. So no, we're not focused on this feature at this point. Contributions are always welcome, especially with...

@RobertJGabriel that project looks like it could be very valuable for this feature. Thanks for mentioning it!

Thanks @ianonavy and welcome! Glad to have you :) @revel/core any thoughts?

Yes, proxying/exposing the needed functionality would be a good solution. I don't think the currently exposed interface would perceivably change. The restructuring would be only internal. Is there something I...

Checkout the [revised roadmap](https://github.com/revel/revel/wiki/Roadmap#v012-see-issues) and specifically the "Create subpackages" list item. Does everyone agree that this list is reasonable and complete? Are there any other Revel components that should be...

@NitroKKX when I say "subpackage" I mean exactly what you are thinking of: a subfolder inside the Revel core package that is then imported by the top level Revel code....

@anonx that's a possible package, but it seems it might be better as a more specific set of util packages instead of some catch all package. What do you think?

@NitroKKX Good point about moving the `watcher` to `cmd`. As for the coupling of `router` and `server`, I'll have to look closer to see what can be done, but separation...

@anonx isn't `Params` also related to binding? Perhaps we should combine it into the `binding` sub-package?