-
Notifications
You must be signed in to change notification settings - Fork 730
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
Roadmap for the next versions #175
Comments
This sounds like a solid plan lets try to commit to it :-) |
this sounds like a good plan, thanks a lot guys. |
I will apply those milestones :) |
@goanpeca could you take a look in behavior of the latest version on spyder? I think that is ok about the buttons. So, we can create a new release for v2.7 if it is ok :) Tks |
Yes i can, doing it now |
@dpizetta things are looking good :-p Only the close in the tabs is a bit too small, but maybe we are adding a custom CSS and that is why Also the toolbar buttons inside the dockwidgets are cropped, but it seems to be a MAC thing only (also maybe we add a custom CSS need to check) Thanks for working on this :-) |
@goanpeca Tks! Updating to master branch both qdarkstyle and spyder, reseting everything I get this: I recommend you to test those issues with your example to see if it is from spyder or from mac. I will create a release for this version, so other people can use from pypi. |
Hi @goanpeca, just to let you know and to keep the repo more organized, I created a new branch "develop" for the latest development. The branch "dev" I will merge with the develop" and then kill it : 0. So we keep the master only for stable versions. Tags will be pushed to master also. We can create temp branches for release too, following gitflow. Suggestions? |
Sounds good to me :-) |
Will do @dpizetta |
Hi guys @ColinDuquesnoy @ccordoba12 @goanpeca. I'm thinking about changing the roadmap a bit as we have changed some points after the contributions from Spyder team started. Also, the v2.7 is getting bigger :)
Word establishments (I'll point this in the docs also):
Thus, we can remark this:
v2.7 try to reduce the number of issues important for the user, removing developer ones, thus the users can use the fixed things up to now;
v2.8 use only QtPy abstraction + HelpDev for checks, so we can reduce the code, many imports and try's that checks the binding before insert ideas of PR Add pyqt5 support to load_stylesheet() #135. Also we can reduce the number of compiled things - see the case of 'example' in dev version v3.0. However, we keep the same calls!
v2.9 insert those skipped issues to this version - more developer changes, change the call slightly as mentioned in PR Add pyqt5 support to load_stylesheet() #135;
v3.0 change in the API to use only one call setting the binding using QtPy abstraction.
Also, we can match with the Spyder roadmap to reach its needs for v4.0. If everyone agrees I can create the milestones and distribute the issues. Thank you all
The text was updated successfully, but these errors were encountered: