Some sort of release numbering system about ep_draw HOT 7 CLOSED

+1 semver

I thought I replied to this.. I guess not.. Somethings we need.

• Full Front end Test coverage
• Passing load tests
• Refactor
• Clear API design
• Support different databases
• Better Documentation

I don't think adding features should even come onto our radar for quite some time

from ep_draw.

Happy with semver my vote is for

refactor
Multi database support
Full test coverage
Passing load tests
Travis and sauce supports
Full documentation
Decide on how we're handling race conditions and multiple edit collisions (IE O/T?)

from ep_draw.

Okay, that sounds good. Should I open an issue for each of these? According to semver the initial development release should be 0.1.0, and Github helpfully has a milestone system so issues can be marked toward 0.1.0.

from ep_draw.

Yea, please :)

Let me know if you are going to be contributing a fair amount and we can setup code reviews and get you setup as a collaborator.

from ep_draw.

I think I will be collaborating a fair amount. I can get to work on some of the frontend issues, as CSS is sort of my specialty, but I can also do plenty of backend stuff.

Should I open the issues on this repo or on JohnMcLear/draw ?

from ep_draw.

Excellent :) open the issues on JohnMcLear/draw for Etherdraw and this repo for the Etherpad Plugin (which there shouldn't be many issues)

Jiust realized this issue is prolly in the wrong place cc'ing @tranek who has contributed a lot to this project and will have some opinions.

Apols for the double post earlier, I'm just getting back to my battlestation after some time away and should be more coherent..

from ep_draw.

I'm all for release numbering systems. No complaints here :)

from ep_draw.