Skip to content
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

Initial draft of roadmap #15

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Initial draft of roadmap #15

wants to merge 3 commits into from

Conversation

kball
Copy link
Contributor

@kball kball commented Oct 4, 2016

We need to get out ahead of our planning and roadmapping for Foundation. Not that we won't be flexible and change, but we need direction and focus. This is a pass on a roadmap... it is almost certainly missing some things, so please jump in and add feedback, things you want to make sure get prioritized, etc.

@brettsmason
Copy link
Contributor

So I've had a good read over it - thanks for putting this together.
My comments:

6.2.4
All sounds fine to me. Definately need to get on top of the issues and PRs some how, though not sure how as there are so many!

6.2.5
Again sounds fine.

6.3
The February release date concerns me to be honest. I cant remember exactly when we started commiting to 6.3, but 6.2 came out towards the end of February. That would be nearly a year for that release. I cant remember exactly what, but there's been some great PRs added (I remember some from designerno1 to do with Drilldown off the top of my head) and I'd hate for interest in these new features to dwindle too much. I'm not sure what can be done about it though, other than do we need a 6.2.5?

Agenda wise I'd like to look at vertical rhythm as I think that would be a huge plus, and its not handled by other frameworks. This would require some Zurb input though on some decisions/direction of travel.

Overall its fairly JavaScript heavy, but I know there is more work to be done there. I'll see if I can think of any larger Sass issues that could be tackled along the way too.

@Owlbertz
Copy link
Collaborator

Owlbertz commented Oct 5, 2016

I agree with @brettsmason regarding 6.3. In my opinion we should consider skipping 6.2.5 to get 6.3 out sooner because of the PRs that went in.

@kball
Copy link
Contributor Author

kball commented Oct 5, 2016

Thanks for the feedback @Owlbertz and @brettsmason - I just pushed up an update moving 6.3 in and incorporating some of the features that are already in PRs for 6.3.

@zurb/yetinauts any other folks have opinions & feedback?

@kball
Copy link
Contributor Author

kball commented Oct 6, 2016

@ncoden would love your thoughts on this as well

@ncoden
Copy link
Contributor

ncoden commented Oct 6, 2016

@kball Why ? Because I have some PR in 6.3 ?

What I'm waiting for is the next major breaking release 7.0, to break the scss ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants