Problem/Motivation

We need to support the latest Bootstrap 3 release.

Proposed resolution

Upgrade the 7.x-2.x branch to BS3 on 7.x-3.x.

Thanks contributors!

   # of commits per contributor
    82  @Mark Carver
    27  @valkum
    15  @el7cosmos
     6  @wundo
     6  @heylookalive
     5  @tripox
     4  @ShaunDychko
     4  @herom
     3  @Denes.Szabo
     3  @kslonka
     1  @danillonunes
     1  @brian_ak
     1  @balintk
     1  @albertomota
     1  @thumb
     1  @Adam Wood
     1  @duncan.moo
     1  @pebosi
     1  @smoothify
     1  @geodaniel

7.x-3.0 [release notes]

7.x-3.0-rc2 [release notes]

7.x-3.0-rc1 [release notes]

7.x-3.0-beta1 [release notes]

Original report by @wundo

As we discussed on our Skype call let's create a 7.x-3.x so we can start postponing some features requests to the next version of this module + draft some roadmap.

Files: 

Comments

Title:[meta] Create 7.x-3.x branch[meta] 7.x-3.x branch development roadmap
Version:7.x-2.x-dev» 7.x-3.x-dev
Issue tags:+meta, +7.x-3.x

Branch created! :)

Changing the topic to "7.x-3.x branch development roadmap"

https://github.com/twitter/bootstrap/pull/6342

Perhaps it would make sense to limit support of Bootstrap 2 to the 2.x branch and Bootstrap 3 to the 3.x branch, thoughts?

Marked #1990236: Bootstrap 3.0.0 as a dup of this issue.

Title:[meta] 7.x-3.x branch development roadmap[meta] Bootstrap 3.0

I'm going to re-purpose this issue. I went ahead and updated the project page to reflect that the 3.x branch will be developed once a release for Bootstrap 3.0 has been made. I think this will be the best approach. I know that the original intent for this branch was to try and merge all the different projects into this one, but given the lack of interest/time committed to it, I'm thinking that can be averted now. I'm OK with patch submissions to include/fix solutions from other projects.

If anyone really has the time or the desire to start from scratch, they should instead start a sandbox (edit: and provide patches to merge them in).

Title:[meta] Bootstrap 3.0Bootstrap 3.0
Issue tags:-meta, -7.x-3.x

Removing meta tags since this is the main issue.

Assigned:wundo» Unassigned

Unassigned wundo until we know what needs to be done and by whom.

Bootstrap 3.0 RC1 finaly released http://getbootstrap.com/. Maybe some work can be done on the 7.x-3.x version now?

Patches are welcome ;)

Hmm... that's interesting. Perhaps I can scrap 8.x-2.x and just do 8.x-3.x then back port that to D7? Thoughts?

I agree @Mark Carver. When 8.x-3.x is stable Bootstrap 3 will probably be stable as well (looks like August 19).

We'll probably have to wait until https://github.com/netdna/bootstrap-cdn/issues/147 as well.

Version:7.x-3.x-dev» 8.x-2.x-dev
Component:Miscellaneous» Code
Status:Active» Postponed

Moving to 8.x branch (even though it's 2.x) and marking this postponed for now.

Is there going to be a drupal 7 version too.
I heard acquia recommend not to update clients
websutes to Drupal 8 until at least a year after it's release.

Yes, that's why I tagged it as "Needs backport to 7.x-3.x".

Version:8.x-2.x-dev» 7.x-3.x-dev

#19 Edit : My mistake, sorry.

Please read an issue before asking questions (or changing a status) that have already been answered (see #14 and #15).

I have modified 7.x-2.1 upgraded to Bootstrap 3, It works very well,Only a few changes.

Bootstrap 3.0 main changes:Migrating to Bootstrap 3

That's great news Laogui!
Thank you :)

Version:7.x-3.x-dev» 8.x-2.x-dev

I'm about to temporarily lock this issue. Yes there are things in 3.x that is just a "straight conversion". But there is also new features that need to be added and old features that need to be removed. Plus I would like to refactor the code a bit so the base theme is not so override-happy when it isn't really necessary. There's also the sub-theme starter kit, the drupal "overrides".... Sigh, it's a little more complicated than just a simple search and replace of existing "classes".

Don't change the status. This helps prioritize things for maintainers. Besides, this is an "RC" not an actual release (in case you were wondering why it's not a "huge" priority).

Now bootstrap 3 is on RC1 release, I think it will be released quite soon.

When you go on http://getbootstrap.com/, the page consider the boostrap 3 as the "thing to download" and put a small link for bootstrap 2 if you want the "old one".

So I think the work on bootstrap 3.x branch should begin to have a Drupal bootstrap official release when the Twitter Boostrap official release come out.

Personnally I think that the approach with Drupal 8 is different than the others (I use Drupal since 5.0). This time, we have majors changes on the Drupal API as it was based on symphony. That means that Drupal 8 will not be usable several month after the official release...

Too much things have changed and even the 7.x was not usable immediatly after the official release even with the D7CX project.

As we have a good 7.x-2.x version of Bootstrap based on Bootstrap 2.x, it would be better to work on a 7.x-3.x version first. Changes are quite minimal between 2.x and 3.x and it would make Drupal usable with bootstrap 3 by waiting a strong 8.x version (strong means with all majord modules compatible).

Without that, I'm afraid to see that we could have a big gap between a 8.x-3.x version of Bootstrap (but unusable because all other modules are not ready yet) and an obsolete 7.x-2.x version only compatible with Boostrap 2.x.

That means that Drupal 8 will not be usable several month after the official release. Too much things have changed and even the 7.x was not usable immediatly after the official release even with the D7CX project.

Yes this was true for 7.x, but it was primarily because Views didn't get ported to 7.x until about 6 months after D7 was released. Views is in core now. There is a lot of things that have been added to 8.x to make building a site rather feasible (even now). Aside from some major and critical bugs, I have noticed that 8.x is a lot more stable than any other release of Drupal. This is partially due to the massive amount of testing that's being done now (literally tests for everything), but also because of the the Symphony framework. More things are OOP based and have provided more structure and helps weed out the "oops, gotchas" that comes with more procedural code.

As we have a good 7.x-2.x version of Bootstrap based on Bootstrap 2.x, it would be better to work on a 7.x-3.x version first. Changes are quite minimal between 2.x and 3.x and it would make Drupal usable with bootstrap 3 by waiting a strong 8.x version (strong means with all majord modules compatible).

"Good 7.x-2.x version"... hmm. Yes, it's "stable" but hardly good IMO. This project has undergone huge refactors, merges, direction shifts, [co-]maintainer shifts (even before I got involved)... you name it, it's been done. The base theme could use a good overhaul.

Porting support of a library is not simple as you might think (I'm not talking about just code here, a lot of it has to do with conceptualizing a bigger picture for moving forward). Yes at first glace it seems to be relatively small changes, but they have added/removed/changed a ton of things from 2.0 -> 3.0. Just look at the commit logs since they released RC1 (https://github.com/twbs/bootstrap/commits/3.0.0-wip). They have 10 pages of fixes, additions, removals, doc updates.

This is why I want to wait. I get that this "shiny new toy" is the direction we're headed, but it is no where near stable enough to port yet. This is why I postponed this issue.

Without that, I'm afraid to see that we could have a big gap between a 8.x-3.x version of Bootstrap (but unusable because all other modules are not ready yet) and an obsolete 7.x-2.x version only compatible with Boostrap 2.x.

In regards to the 8.x status, please read the Backport Policy.

And before anyone quips off: "But the Backport Policy only has to do with core". Nope, that's not true. It's a general concept of how many developers/themers work in the Drupal community. We work off of HEAD, in this case HEAD (even in Bootstrap) is D8. Now this doesn't mean I won't start working in tandem with the 7.x-3.x branch, but in reality everything should be against 8.x first with a backport to 7.x.

I'm not sure module will come faster on Drupal 8.x than 7.x. Ok we have views in core which can help, but on the other hand, we have a complete new API heavily OOP and based on symphony. It's a huge change for module developper and they will probably need to be completly rewritten, not easily upgraded as before.

Each major drupal release, it's the same thing. Optimistic people vs Pessimistic people. Time and personal experience made me to change my side from optimistic people to pessimistic, but you are the module maintainer, I don't have time to give to drupal community ATM so I shut up and do what you want :)

For the upgrade from 2.x to 3.x of bootstrap, I suggest you look at this post instead of the bootstrap issue queue that contains a lot of useles things for users and it could discourage for the upgrade that is not so important.

But I'm agree with you that the Bootstrap module (the drupal one) need some revamp to be easier and more logical to use, that's not related to the Bootstrap (the twitter one) upgrade path but it can represent a lot of work.

Alex

For the upgrade from 2.x to 3.x of bootstrap, I suggest you look at this post instead of the bootstrap issue queue that contains a lot of useles things for users and it could discourage for the upgrade that is not so important.

Yes, I'm well aware of that post. And...

But I'm agree with you that the Bootstrap module (the drupal one) need some revamp to be easier and more logical to use, that's not related to the Bootstrap (the twitter one) upgrade path but it can represent a lot of work.

is exactly my point. The upgrade isn't just "Bootstrap" specific, but has more to do with the existing integration of Drupal specific implementations. Upgrading this project won't be as simple as swapping out a few classes.

Hey guys! any new developments on bringing bootstrap 3 to drupal 7?

Read http://blog.getbootstrap.com/2013/08/13/bootstrap-3-rc2/

That is all that has changed in just ONE release (rc1 to rc2). Please... stop asking. I doubt any over us maintainers will start working on the 3.0 version until a stable solid release has been made.

I think we need this very clear stated on the project home
page to stop people asking all the time

I hope that's helpful :)

Thanks @charlie charles, I went ahead and updated the project page.

I'm wanting to start using Bootstrap for my site (currently using AdaptiveTheme). Can someone familiar with the upgrade from Bootstrap 2 to 3 give me some advice?

Should I should re-theme my site now for Bootstrap 2 and Drupal 7 and then upgrade in less than a year to Bootstrap 3 and Drupal 8? Or should I just ride out Drupal 7 with my current theme and start fresh for Bootstrap 3?

Right now I'm thinking all the hard work for the upgrade to Bootstrap 3 will be done in this theme project, and the sub-theme I make will be pretty simple to upgrade. But that's a really naive assumption. I also plan on using LESS which should make my sub-theme simpler.

I'm wanting to start using Bootstrap for my site (currently using AdaptiveTheme). Can someone familiar with the upgrade from Bootstrap 2 to 3 give me some advice?

Depend really what you want from the theme to do?

The main update of bootstrap 3 is it's mobile 1st.

I find the AdaptiveTheme works better than bootstrap 2
when I using drupal responsive image modules

Omega drupal theme has been mobile 1st for a long time now.
So what Bootstrap 3 is offering nothing new compared
to existing drupal themes out there already.

Bootstrap is easier to use than omega
and that's why I like to use it

I hope that helps

I doubt any over us maintainers will start working on the 3.0 version until a stable solid release has been made.

Bootstrap 3 released: http://blog.getbootstrap.com/2013/08/19/bootstrap-3-released/

just FYI.
cheers, Ronald

Version:8.x-2.x-dev» 7.x-3.x-dev
Status:Postponed» Active

Indeed... they certainly pushed that through fast didn't they. Hmm.. well regardless, I myself do not have the time (see: #14) right now to focus explicitly on this. However, I'd certainly be happy to mentor anyone that would like to submit patches to help get the ball rolling until I can commit more resources to it.

Moving this back to 7.x-3.x as this most certainly will be where this happens first now.

The 7.x-3.x branch is basically empty at the moment. I'll merge 7.x-2.x into it so it's updated to the latest dev (that way people can start patching it).

Title:Bootstrap 3.0[meta] Bootstrap 3.0
Issue tags:+Needs issue summary update

Merged 7.x-2.x into 7.x-3.x.

Create new issues to patch against the 7.x-3.x branch. This issue will serve as the META for all sub-issues. Please keep the issue summary as up to date as much as possible too.

Once an actual beta/rc release is made for the 7.x-3.x branch, this issue should be fixed.

This would be a great help

http://getbootstrap.com/getting-started/#migration
http://bootply.com/bootstrap-3-migration-guide
http://upgrade-bootstrap.bootply.com/

I'll try to work on and submit patch as soon i got free time

StatusFileSize
new1.53 KB
new27.01 KB

Hello!

I did some work on 3.0, patch and script included. Will continue to work tomorrow.

PS I'm a newbie so don't scream at me if I did anything wrong ^_^

As #22, i don't think the bootstrap 3 changes is just about class name. There's also changes in HTML markup structure like navbar and grid system. And new feature should be implemented.

@el7cosmos, agreed. There is definitely more to migrating from 2 -> 3 than just classes. Would you mind maybe updating the issue queueissue summary and creating sub-issues to iterate over? I would greatly appreciate it! I think we would all benefit if we had a clearer direction in mind so we can focus on the individual tasks that are needed :)

@kslonka, thank you very much for this patch :) I don't condone "screaming at n00bs" so you're safe :-p This definitely helps get us on the right start. I would, however, prefer if we did smaller patches (also in a new issue) per my request in #36. This helps focus on changing certain aspects of the code, rather than just a large patch that does a "find and replace":

+++ b/includes/form.inc
@@ -23,12 +23,12 @@ function bootstrap_form_alter(&$form, &$form_state, $form_id) {
-  $form['#attributes']['class'][] = 'form-search';
+  $form['#attributes']['class'][] = '';
@@ -45,11 +45,11 @@ function bootstrap_form_search_form_alter(&$form, &$form_state) {
-  $form['#attributes']['class'][] = 'form-search';
+  $form['#attributes']['class'][] = '';
+++ b/includes/menu.inc
@@ -53,7 +53,7 @@ function bootstrap_menu_local_task($variables) {
-  return '<ul class="menu nav">' . $variables['tree'] . '</ul>';
+  return '<ul class="">' . $variables['tree'] . '</ul>';
@@ -77,7 +77,7 @@ function bootstrap_menu_link(array $variables) {
-        $element['#attributes']['class'][] = 'dropdown-submenu';
+        $element['#attributes']['class'][] = '';

Things like this tend to happen. This is technically inserting blank classes when they should, in fact, just be removed. :)

There is also some other logic happening to the CDN that could probably be simpler. The 7.x-3.x wouldn't support Bootstrap 2.0, so we could take those out.

@Mark I'm not clear with the "updating the issue summary and creating sub-issues to iterate over" workflow, lets say i start with patching less in bootstrap_subtheme, then i create new issue with 3.x branch, then what should i do?

For issue summary instructions, see http://drupal.org/issue-summaries. I'll update it with a bare template for now (also see Dreditor to help with speeding up this process).

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Update remaining task

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Update summary, remaining tasks

It is waiting for at least a crude version of the theme for the third part. Now does not want to start new projects on older second bootstrap. Unfortunately, I can not help with the development, but at least the test and began to apply immediately after its release. I'm going to dance when it's released)

I really don't know why there is this sudden idea floating around that BS2 is suddenly "bad" because BS3 came out. If your project cannot wait for the Drupal port of BS3 (which I have no idea when it will be released, which is why this is open source), then use BS2. It's not like BS2 is broken or something...

@mark do you have any idea at all on an timeframe you're shooting for? I've got a few projects coming up which will be BS3 and would like the theme to be v3 also, that said yep can use branch 3 + patches.

Additionally if you'd like help let me know, you've mentioned that you'd like to change a few bits, could you elaborate? Otherwise can work on the bits that need it.

BS2 is a cool thing, especially for Drupal theme v2. I use it in many projects and more will be using. Still, progress is not in place and wants to have more and a new tool, I do not think the same.

@heylookalive: Honestly, idk. There's not real set "goal" atm and quite honestly this project is at the bottom of my @todo list for the time being. Just help with creating patches against 7.x-3.x. I'll review/commit them when I can.

@TheJoker: There is progress being made, look at the issue summary at the top.

@mark OK, with that in mind could you show the 3.x dev branch as available on the project page, that way people will see things are active. There are patches ready for review on the issues listed in the summary. If you don't have time then I'd be happy to help co-maintain if you were open to it :)

@heylookalive, I'd rather not just yet. Once a beta release is close, I will. As far as petitioning for co-maintainership, you'll have to ask @wundo. He is in charge of the actual project itself. However, that being said... I have probably been the only "active" maintainer for a while and there's already a long list of people with commit access.

FWIW, I do give feed back and commit patches when appropriate rather quickly. I get emails each time there is a comment on an issue in this project, btw. So you don't have to worry about things getting "stale". I'm just currently in a transition period between jobs, so at the very least I'll be able to test/review more on weekends for the time being.

I'm really excited to hear progress is being made towards a 3.0 release.

@heylookalive, you are everywhere brother! Harmony and Bootstrap 3.0.

Issue summary:View changes

Added separate issue for grid migration.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Updating tags

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Thanks for all your great work Mark!
This Drupal Bootstrap project getting better and better!

This seems close enough for a dev branch

Issue summary:View changes

Updated issue summary.

Hi guys,

I'd be more than happy to sponsor a few hundred dollars to get v3 Bootstrap working in this theme. Require it for a job I'm currently a part of....

Me too, I'll pitch $100 if this can be finalized in the next 2 weeks. If one of the project maintainers can please PM me their PayPal address, I'll make it so.

Maybe you'd be interested in https://www.gittip.com/for/drupal/ since it's getting more and more popular within the community those days? Would allow you to make a smaller but recurring payment.

Which gittip is for the drupal bootstrap project?

I think https://www.drupalfund.us/
might be better option for payment for upgrade
from bootstrap 2x to 3x

FWIW, I do have a gittip account: https://www.gittip.com/markcarver

Issue summary:View changes

Added in more issues.

I am writing on behalf http://drupalfund.us - we would be happy to help raising funds to help deliver Bootstrap 3.0

@Mark Carver & @wundo if you are interested ping me, I will be happy to help setting up the project and explain how Drupalfund works.

You can also listen to podcast on Drupalfund: http://modulesunraveled.com/podcast/078-drupal-fund-us-jozef-toth-module...

Hi Mark,

Just putting through US$250 to help get this stable. Please PM me when you have an update.

*** Update *** one-time payments cannot be made via Gittip that I can see. Please let me know how to contribute.

@mark if you're funded are you able to commit to a date for a release?

I don't like gittip, it seems to be a recurring system. I'd just like to chip in a one-time. $100
A PayPal donate button on the project page??

Issue summary:View changes

Updated issue summary.

We're almost there. There's been a lot of patches submitted and committed recently and I'm going through them as quickly as I can :) Great work everyone! I personally prefer Gittip because it is a continuous contribution, which helps many projects (not just a specific one). I don't have the real resource (time) to solely commit to just one project, but am able to push patches when they're RTBC. If you would like to offer a "one time contribution", hit up some of the other guys (mainly @heylookalive) who are the ones who are actually working on this project. I don't think it's fair for me or @wundo (who hasn't been active in months) to take a large one-time lump sum for something that is as simple as pushing RTBC patches.

Also FWIW, Gittip is more in-line with an "open source" modal than just paying a one time contribution. Those of us who maintain these projects do so out of our own pocket/sleepless nights (day in and day out, ie: reoccurring). I would strongly recommend offering smaller and reoccurring contributions to those who actually do work for open source projects instead of just whining that things aren't on your time table and trying to bribe them for singular focus.... just saying.

@heylookalive, in answer to your question on a "release date", I would suspect that with your awesomely hard work we could perhaps have an RC1 within the next week! Thank you!

Good hustle guys :)

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Just released 7.x-3.0-beta1 (https://drupal.org/node/2094423). The packager seems to have hung, but once it's done it will show up on the project page. We still have a lot of tedious cleanup/polishing to do for rc1, rc2, and subsequently 3.0. Please file any and all new issues against the 3.x branch (regardless of what version it is on). I would like to start getting people to test the beta as it is somewhat manageable now.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

This is excellent, 3.x beta 1 is now up :)

Should anyone want to chip me a few bucks I'm on Gittip here, it would be greatly appreciated, but not necessary :) https://www.gittip.com/heylookalive

Hmm, in light of Omega launching 4.x on Tuesday at DrupalCon Prague (and in the spirit of healthy competition lol), if people are willing to pitch in the next few days we might be able to just skip rc and punch out a full 3.0 release around the same time. What do y'all think?

Issue summary:View changes

Updated issue summary.

Why not go for a BoOmega?

Else stick with what you got.

What is with third-party issues? Like Views-UI.
I'm not sure if its good to release two big themes the same time. And as there is no Bootstrap session maybe the full release will be unnoticeable .

I'm just happy the bootstrap 3 theme nearly finished :)
Thank you to everyone who made it happen! :)

@heylookalive: Gifting $100 a week for a few weeks for your work on this.

@webindustries, totally not the point of Gittip, but um ok :-/

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

@Mark Carver,

Understand it's not ideal, but for a company wishing to support a project - whilst managing their own finances - donating in whatever possible form is better than not. First person ever to moan about a project being financially supported in some form. Nice one.

I'm sure heylookalive isn't complaining. Mark, there isn't a wrong way to make donations.

First let me preface this with saying that I am not attacking anyone. I am simply explaining my point of view and experience with managing free projects on drupal.org.

In #63, I was attempting to make clear that there is not just one individual who deserves financial contribution. In fact, if one were to read the commit log for the past few weeks, you would see the following people contributing to making Bootstrap 3 a (soon to be) reality:

@valkum, @kslonka, @heylookalive, @tr33m4n, @el7cosmos, @tripox, @Denes.Szabo, @danillonunes

I commend these guys sooo much! Bravo!!!! They have increased the quality and vitality of the Drupal Bootstrap project tremendously!

And of course there is myself, who has been prioritizing, organizing, coding, reviewing and committing everything over the past few weeks (in my spare time.... for free).

What I'm confused with is the willingness to spend upwards of $300 on a single individual, who may or may not have the time over the next 3 weeks, to accomplish a task that will more than likely be done in half that time (by the community as a whole, I might add). Instead of:

Supporting each of these (9) contributors. Even at just $1/week (and assuming they all have a gittip account), that would still only put anyone out at a maximum of $36/month. A far more effective business venture I would suspect... but what do I know, I'm just a code monkey for hire, right?

No one person can do everything, that's why we (as an open source community) rely on multiple people. So on some level, openly supporting someone (and announcing that amount in a public venue) so.... yes, I'll admit that part is just a little insulting to all the others that are involved.

As a maintainer of several Drupal projects, I am very and deeply passionate about ensuring the equality, fairness and openness to all. I consider it part of my "job" (if you will) to advocate of all people involved, especially in the event when monies are involved. These awesome and amazing people are the ones who actually do the work it takes to bring you stunning and amazing web technologies (which are often for free).

First person ever to moan about a project being financially supported in some form. Nice one.

I'm certainly not opposed to money, but how one goes about it in an open source environment (considering the many parties involved), that's another story. I sincerely hope no one takes my words above as an "attack" as they are not meant to be.

As always I encourage all to help further support this cause... even it just be creating them there patches ;) I personally though, would take a patch over money any day lol

Quick note that I've just tried out some of what Bootstrap 3.x is and can see so much more improvement for its use over 2.x in the Drupal world. Well done, team, this is awesome! So glad to see this become as great as it is. See you in the queue!

So we don't sidetrack this issue I've created a new one over here for the donations stuff, I feel like we can work this out :) #2096519: Bootstrap 3 donations Many thanks to @webindustries for supporting the community!

Its nice to see @RobLoach here!

#75 I'm with you @Mark. While it is true that there is no wrong way to make donations, i can see what mark trying to tell us. I honestly think that will be very good for community

If you all spent as much time finding a proper sponsorship medium as you do talking about the rights and wrongs of a company willing to inject capital into a project, Drupal and this project would even stronger...

Stop complaining and appreciate the donation - however that may come about from a willing partner in the community.

i dont think @mark, me, or anyone in here talking about what is rights and what is wrong, nor complaining. And im sure your donation will be very much appreciated

@webindustries, yep what @el7cosmos said. We're very grateful for the donation and happy that you're supporting the community. You can let me worry about distribution etc. This element of the discussion continues over here #2096519: Bootstrap 3 donations

Otherwise we can have this issue be back on track for managing the BS3 release we'll all enjoy using :)

@robloach thanks, good to see you here!

Wow... ok lol yes, moving on

Wow Looks amazing everyone! Keep up the good work!

Issue summary:View changes

Updated issue summary.

Hey guys, nice community work on 7.x-3.x branch!

Honestly I share the same feeling from Mark Carver about funding, but I think we should move on and use this track to what it was intended when I originally created it which is code.

I've just committed kslonka's patch for #2095417: Update grid variables and added also a commit of mine to it.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Should we push the remaining feature request to 3.1 release? I'm not sure if these issues prevent bootstrap from releasing soon.

Release RC1 when #2096557: Fix <body> paddings for with fixed navbar/admin toolbars is fixed
And RC2 when the new favicon and logo is finished?

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Bootstrap 7.x-3.0-rc1 is ready for testing! I strongly recommend everyone to read the release notes. A lot of work has gone on since the initial beta. As this is the first release candidate, there will be bugs. Please create new issues appropriately so we can address and fix them for RC2.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

I've added the number of (current) contributor commits to the issue summary: https://drupal.org/node/1840980#summary-contributor-commits
This will be updated periodically and one last time before the funds are distributed on Nov 1, 2013.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Hey everyone! @tripox added some awesome new favicon options at #2094413-3: Create new favicon(s)?, check them out and let us know which one makes you smile :)

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

An awesome new logo and favicon we're just committed! Check it out on the project page! Thanks @tripox!!

Issue summary:View changes

Updated issue summary.

Great work, everyone! Even at RC1, Bootstrap 3 is my new favorite theme. :-)

I know I'm a bit late to the party, but I ported the 2- and 3-column default Panels layouts to use Bootstrap grid classes so they'd be responsive. Any interest in adding them? If so, I'll attach a ZIP or try to create a patch. Your call.

@ComboPrime, please see my comment at #2043193-3: Include Bootstrap Panels With Theme. Thanks!

Logo looks great! Good work @ tripox.

@ComboPrime, I would like to play around with your Panels layouts. Let me know where you end up posting them.

@Mark Carver: Sorry I didn't see that! Will have to try it out, thanks.

@animelion: For now, there's a ZIP archive available here: Bootstrap 3 Panels layouts. You'll also need to add a line to your theme's .info file--see Step 3 at Creating a custom layout in your theme.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

added #2094179 to bugs

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Thanks everyone for the AWESOME feedback and extensive testing!! We've just released 7.x-3.0-rc2! Be sure to continue testing it! We're on an awesome path to the final and official release of 7.x-3.0 in just a couple weeks!

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Updated issue summary.

Issue summary:View changes

Issue summary:View changes

Due to the recent drupal.org D7 upgrade, my attention has been solely focused on updating Dreditor (so it could be marginally functional) in time for the launch today. This migration was announced after this project's original intent to release a full Bootstrap 7.x-3.0 release on November 1st.

There has been an enormous amount of testing of Beta1, RC1 and RC2! Thank you all! We are certainly close to accomplishing this feat, but will need at least one more week, possibly two, to ensure we release a solid version.

Please check the remaining bugs and tasks on our META issue: https://drupal.org/node/1840980

Feature requests may or may not get included, depending on if a patch is submitted.

Due to the extension in a full release, I am also extending the PayPal registration deadline. Contributors who have provided patches (and were committed) and wish to receive a portion of the funds must submit their PayPal information via my https://drupal.org/user/501638/contact form before November 8th.

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

I will be releasing 7.x-3.0 this Sat, Nov 16th. Please test the dev version extensively in the next couple of days. Only really major bugs will be addressed before the release. All existing feature requests or new issues created will be postponed for 7.x-3.1.

Issue summary:View changes

Added the Panels IPE bug (found in latest 3.x dev) to which I've attached a working patch

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes

Issue summary:View changes
Status:Active» Fixed
Issue tags:-meta

Bootstrap 7.x-3.0 is now released!
https://drupal.org/node/2137547

I am now marking this issue as fixed (woohoo)! Please do not change the status of this issue. File new issues if you encounter bugs or want new features.

\o/

Status:Fixed» Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.