Hey all,
Thanks for joining the mailing list and taking an interest in the project. This email is a quick summary of what's happened in the first few days since launch, and to let you know what's in store for Jam over the next few days and weeks.
Recent releases
============
There were predictably a few small bugs to iron out and pull requests to attend to as people got their hands on the code. That has meant frequent small releases. I expect the release cycle to become more predictable as the core features settle down a bit.
0.1.0 - First release
0.1.1 - Upgraded prompt library and fixed an issue with encoding URL incompatible characters in auth details
0.1.2 - Updated RequireJS to 2.0.2
0.1.3 - Fix install command when fetching tarballs from GitHub (wasn't following redirects previously)
0.1.4 - Added short-hand versions of many command-line options (eg, -r for --repository). Fixed warnings in Node.js 0.7.x, and relaxed node engine requirements. Added 'shim' support to package.json. HTTP proxy support. Added jamMain property support in package.json.
0.1.5 - Added "search" command
The Future
========
* Jam will be getting it's own website with new features for keeping track of package updates.
* The ability to install packages more easily directly from GitHub, for when you can't find what you need in the official repository.
* Private repositories / multiple package sources - ability to run your own package repository behind a company firewall.
I think there's a lot we can do to continually improve the experience. As always, I look forward to your feedback.
Coverage
=======
In addition to the buzz on Twitter, there has also been some other interesting coverage around the web.
- - - - - - - - - - - - - - - - - - -
If you have any feature requests or bug reports, add them to the GitHub Issues:
For support, discussion etc. Post to this list.
Thanks all, keep Jammin'
Caolan