Closed wreiske closed 5 years ago
I don't have time to maintain this project anymore, so I gave you commit access to make any changes you'd like. It would be nice to follow the style used by the rest of the code and add some tests to this patch, if possible.
If you'd like to directly publish new versions of the package, just send me your Meteor username and I'll add you as a maintainer.
If you'd like to directly publish new versions of the package, just send me your Meteor username and I'll add you as a maintainer.
Awesome, it'd be an honor. I use this package religiously across multiple projects.
My meteor username is: wreiske
Thanks!
Awesome, you're in! If you want to help maintain anything else, like https://github.com/mizzao/meteor-user-status which uses this a lot, happy to add you there as well.
I usually use the following simple procedure for publishing, although you can do what works for you:
History.md
file to reflect all changes that will be in the new version. If you've been keeping it up to date (and it appears you have), this just involves inserting the above version number below vNEXT.package.js
.meteor publish
git tag v0.x.y
and push the tag (git push origin v0.x.y
; this allows others to find the code for this version) and merge into master and push that too. (If you aren't rebasing the feature branch you may want to merge first before publishing)Thanks so much for your help!
I'm working on a meteor-desktop app for work and ran into an issue where the TimeSync was returning NaN. This pull request fixes it, allowing TimeSync to work correctly in meteor-desktop clients.