merge master to dev and push to dev from now on

[belevtsoff]

as we agreed:

• push to dev until the next release is ready (creating branches for features and large fixes if needed)
• merge dev to master
• tag the release

[btel]

We should move the commits from master to dev. Do you know how to do that?

[btel]

I have just added a short guide describing our development practices to the wiki pages: https://github.com/btel/SpikeSort/wiki/Developers-Manual. Please comment!

[belevtsoff]

wiki: cool, that's a nice place for such meta-information.
move: dunno yet, will google it

[btel]

I forced pushed to master to revert to earlier version of the history and moved all new commits to dev.

[cpcloud]

Cool. No problem.

Best,
Phillip Cloud
PhD Student
CUNY Graduate Center
Program in Cognitive Neuroscience
phillip@phillipcloud.com
www.phillipcloud.com

On Mon, Apr 23, 2012 at 3:24 AM, Dmytro <
reply@reply.github.com

wrote:

as we agreed:

• push to dev until the next release is ready (creating branches for
  features and large fixes if needed)
• merge dev to master
• tag the release

---

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