-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blockers for v1.0 #43
Comments
I agree that 1.0 should be the first full stable release containing some features I would deem required for 1.0. So it's very likely that we will see a 0.10. I'll create a 1.0 milestone to those issues/features I would like to see in 1.0 |
Issue tracking:
|
I could contribute my Docker setup, most up to date here https://github.com/schemen/PlanarAlly/tree/brush I used the brush branch (worked best for me in terms of usage, better than dev). This has already the new assets system integrated as well. You can test a running version here: https://planarally.dndbox.com |
I'll gladly look at your docker setup. I'm currently doing a large behind the scenes UI overhaul changing stuff from manual dom insertions and jquery to Vue, Regarding the brush, I've since combined the brush/draw and fow tools in one singular draw tool as can be seen below. This also means that the brush can be used to draw on normal layers as well :) (note that this change is currently only in the vue branch) |
Wow, this is amazing! I would love to contribute my docker/container experience here and I'll be hosting it as well. I may create a second feature request other than the brush ( Basically a slightly stricter sign up policy) :) Please let me know once you have the "rougher" changes merged into dev, then I'll see to work on a container around it. |
I've just merged Given that a couple of things still are left to do for the 1.0 milestone, I'm planning on doing a 0.9 release with the new stuff since last release. |
I have pushed the new docker image onto dndbox: https://planarally.dndbox.com |
Given that this has not progressed much, I think I'm gonna close the ticket and re-evaluate what I would like to see done for 1.0 |
Was wondering how you are planning to do version numbering in the future. The current one is very simple and straight forward but the next release is 0.9. After that you will reach 1.0 if you don't plan on doing 0.10 etc. Personally in my opinion the 1.0 release should be the first stable release that is somewhat feature complete so it would be nice to keep track of everything in this issue that is blocking v.1.0
The text was updated successfully, but these errors were encountered: