-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
What do we need to get 7.x-3.0 out the door #9
Comments
the only things i need to do on the 3.x branch are related to the hotsauce install profile workflow. i think you can still proceed on 4.x with gusto and i can merge the more backend related stuff i still need to do on 3.x as i go. |
i would honestly would not worry a lot about 3.x ... i just needed to branch because we need to get hotsauce working but 4.x isn't ready to ship yet so i needed someplace to put commits in front of a stable release but still behind you |
I don't think you should add any new backend features to 3.x but any minor improvements and fixes are good. Is there anything I should do for 3.x to get it out soon?— On Sat, May 10, 2014 at 2:00 PM, Michael Pirog notifications@github.com
|
no new features... mostly just bug fixes to get kalatheme to play nice with the hotsauce installer. |
That sounds perfect. I am so psyched to work on this project. I think we're going to have a kickass base theme that is easy to use. — On Sat, May 10, 2014 at 2:03 PM, Michael Pirog notifications@github.com
|
me too. its going to be really awesome! i can't wait for 4.x and the generator to be ready... that is when things are going to get really spicy. |
Can we call the generator 'sauce'?— On Sat, May 10, 2014 at 2:06 PM, Michael Pirog notifications@github.com
|
Is the planck length 1.61619926 × 10-35 meters? |
@pirog I want to start getting 7.x-4.x out soonish. What do you think we should tighten up on the 7.x-3.x branch so we can start really getting onto 7.x-4.x ready.
The text was updated successfully, but these errors were encountered: