Backdrop CMS Weekly, 15 Sep 2016

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Backdrop Weekly 9/15

Description

Today’s development agenda: http://bit.ly/2c3c7wl

A

Hello, everybody welcome to release day it's September, 15 2016. The day that backdrop 1.5 comes out, we're really excited. We've got all kinds of great features that are in the next release and today we're going to be spending polishing up these last couple of items and we're going to be using this meeting to focus exclusively on the release of 1.5, so we'll skip the normal infrastructure, community updates, etc, and just kind of use this as a general kind of scrum.

A

If you will to kind of talk about all of the remaining tasks that are before us and what we need to do before and after the release of backdrop, 1.5 general announcements, no real serious announcements, your kallah box, RC 2, is released with native backdrop, support you can donate to bankruptcy. Ms and you can get a dragon t-shirt and hoodie and bike top semester dorks as / contributes, and if you join the metro contributor, we have lots of phpstorm licenses for anyone that is in the contraband group.

A

You can send us an email info at backdrop, CMS org, and if you are a member of the backdrop in trip group, we will send you a HP storm license.

A

There are no updates from the PMC me this week, and so we will go right in to the backdrop. It's the MS project, progress report so releases.

A

Although 1.5 is coming today. The last release over 1.4 is also coming out today. So that's version 1.4 point 5 that will be released, probably in the next couple of hours. Actually it is good for me to get out one point for the last release with a little bit of breathing room around 1.5, so that we can do one thing at a time.

A

The nice thing about the 1.45 well, there's actually a good 30 or so fixes in that Julius of 1.4, but it also knocks out our last major bug, fixed issue that we've been talking about every week for the past couple of months, which is images frustrating delete. It frustratingly deleted by the prawn, cleanup tasks when you upload an image into a block so that that problem is now fixed.

A

Those images are now marked permanence and they stay around after six hours, which is great, so that will be out shortly in the 1.4 release and, of course, it all off to be in the 1.5 this coming out later today.

A

Okay, so both the items for 150 that we've got um so over and down through the list of what we had marked last week and we can see where we are in each one of those items: the 7 dot, 15, Drupal, 7, dot, 50 cross ports, we've got about half of these completed, but not all of them, and so that's fine.

A

We've got I, think all of the features or API changes, minor API changes that are in that are in that issue into one dot, five, and so the remaining minor items and bug fixes that we have not completed we'll just put those into 151 and 152 or whenever we finish the cross ports.

A

The one that's really interesting out of that series of transports is support for the utf-8 four byte character sets which basically means storing emojis in the database. So that's been finished, imported and elaborated upon, as tends to be our mo we've included in 150, not just the ability to support for by utf-8 characters on new installations, but there's also an in a in administrative area upgrades tool for upgrading your existing websites via batch operation.

A

So, if you're interested in upgrading your site to utf-8 for character for bike characters, you can just visit your status report after you upgrade to 1.5, and it will provide information on whether or not your server supports that feature. What you need to do to enable that feature and a link to the documentation how it works so yeah, so that one's done I need you're, the only one that one's been merged.

A

Okay, next item, the new front, end theme in core basis is issued 1361. This is our last minute item that hasn't been merged yet, but will be merged by the end of the day. So 1361, we kind of stomped logging issues against that large thread, because it's about 90 some comments. Long at this point.

A

So if you find new issues in basis file, a new file, a new issue, if you find a new issue, basically and tag it for the 1.5 Oh milestone and we'll do our best to get it fixed before the release, if it's just a minor, UX thing or CSS, you know tweak here and there we'll do our best to get in every single one of those before the release of 150. But if we don't that's fine it'll, be in the follow-up release.

A

So that's our one item that is still not merged major item the rest of these. It looks really good. The new home page layouts issue 1042 is merged, so we now have a single column home page layouts, which is fantastic in that home, page layouts. We have the new hero block placed by default in issue 1152. That is also emerged.

A

Responsive, drop-down, menus are enabled and turned on out of the box on the home page and all other layouts in issue. 2107 and, let's see, do we have an issue for this? One move permissions for view and unpublished. Contents are more permissions site. We have ability for view any unpublished content, so you can make a editorial administrator essentially, so they can view any unpublished, content without giving them like administered nodes permission or ignore node access permission so basically used. Let them have site-wide, unpublished, content access, yeah.

A

So that's the collection of things that we have, at least regarding that permissions on not so much but regarding the homepage, I think from a marketing perspective. What we're going to be doing probably is having a big tout about basically an all new out of box experience, because, like everything about the homepage, has changed from its appearance to the way that it's built to the things that are on it yeah, it's really its aspects, really awesome, I really excited.

A

Let's see. Originally, we were trying to pitch this release as the editorial experience release. Unfortunately, the items that were key to that reference modulus been kicked to 1.6 and several items in the meta for improving the rich text. Editor is awesome. I've also been kicked to 1.6. We did fix a couple minor things, though we reworked the way that the toolbar buttons work, we're going to add the format's drop-down back to the default toolbar, the Lincoln unlink buttons were missing out of the box for some reason.

A

That was on actually just a bug, but now they have been corrected and there was an anchor tag button that just if you dragged into the tow bar just didn't, do anything and that's also been removed until we get proper support for actually supporting named anchor tags inside of a body content so for all items that are tagged for 1.5, we got them down to just six of them last night, but there it's back up to 13, which are all almost entirely CSS issues at this point regarding basis, so there's really good chance, we'll be knocking those out one up to the other.

A

Here this afternoon, oh, my goodness 1.6. Are we really going to talk about that? Okay, it's been it's being added to our agenda here, so 1.6 yeah, the things that got kicked or bumped reference module and the rich text editor. Those will probably be focus items for 1.6 Jen. Do you want to add something I.

B

Know I was just going to say that we don't have to talk about it, but I wanted to set it up here because we're going to have to talk about it starting next week but yeah, but they put your thinking hats on about what you guys want to do for 16, and we can come up with that next week. That's all.

A

Okay, so, as always, we have either experienced and developer experience issues that we're working on continuously we've actually piled up a huge chunk of UX issues between the.

B

A

And the 150 releases, so if both of those coming out today we're going to see a pretty big jump in a lot of those UX issues, I one of you x issue in particular, is really happy to see. Cleaned up in 150 is that we eliminated the last inappropriate use of the word settings and change it to configure for the layouts Eli sinhala alejo. It doesn't have settings a layout has a configure page. Instead, so I, don't know minor thing, I know, but it's nice.

A

Now we have consistency across the board for what a settings page is and want to configure pages.

A

Now, let's not, let's call it as far as 150 items and not talk about 160 Jenna Rose.

C

Can see we should talk about future fries? Oh.

A

Yeah, just as a possibility, I think that will probably move that too I mean it should be done as a PMC vote. So, but the general proposal is just that this last minute cram, although exciting, it's also really stressful and so for. The next release.

A

160 I'd like to propose that we take a vote of the PMC and establish a feature thrus, but because we will always be moving like we will always move to a more conservative model over time and I know that it's a little bit said to have our cowboy level project move into this level of moderation that we have a feature freeze, but we can start small, and my initial suggestion was this of just that.

A

We push it out two weeks, so we make the first of the month feature freeze, and then we have two weeks in which things and not add new stuff, and that way we'll have a lot more time to plan for things like you know, the muse letter and the marketing and the blog post, and things like that that we can build during that two-week period as.

C

A

Out all remaining last.

C

Issues smashing abs.

B

And user user experience related follow-ups I think that just sometimes when we put in features at the end like stuff gets missed and if we can fit in features earlier, we can go back and kind of make it a little more polished and Lester us is good. I, don't know anyway, doesn't sound like there's any huge objections. We'll talk about it.

D

What well that's knocking at the end this time, what.

B

D

What were the features that snuck in at the end of fun all.

B

D

C

B

C

B

This was go right, so.

D

So what would have made it into the release if we had done freeze.

B

Everything would have been better. Okay,.

C

Yeah, sorry, our dish, it's.

B

Not okay, it's not it yeah go ahead! Me yeah,.

A

If the priests have been there, we would have just done all this work two weeks earlier. That's all that uh that that's our theory, at least.

A

Wet wes is cracking Harry, not so certain about that. Well then, we would have had less things in their release and we would have learned our lesson and then we would have planned better for 1.6.

B

A

All right, I know we're developers and procrastinating is kind of our thing, but but it was like establish some sanity um so sent to headline one month early and then not meet it and then ya know we do have we actually even have a policy around um you know, setting releases and sticking to them and I think that that should apply to our future fries as well, like, let's be serious about our dates and not not be faking them.

A

So if we say that we're going to freeze on on the first before release, then we should stick to it, regardless of the appeal of we could squeeze in this one thing or whatever. Even if that one thing was all a basis.

A

Yeah, exactly anyway, that's not happening this release. um This release, like today's release day basis, is a pull request, but it's going to go in so yeah. That's.

C

Fine changing times that's.

B

Why I think it's also good to talk about it now for 16, because we can possibly have gotten this release it out without advance notice? Everybody knowing that the actual date you need to be done is the first. You can plan around that, but if just like sorry, it's not ready wrapping it and that's totally, not cool so um think about it. We'll talk about it, I will have a pnc vote and then we'll lonely plans for 16 foot. So we know we're doing.

A

Okay, um that's it for the agenda Jen! You want to show off the books again sure.

B

Now that the meeting is broadcasting, so there are two books available for backdrop CMS, um you can get a beginning backdrop book, which is not terribly fat and scary, which is good or migrating from Triple DES backdrop book, which is really tiny cuz. It should be easy to migrate from Triple DES backdrop, um bug them available on a press or Amazon and um yeah. If you are coming too bad camp, you can browse them in person. Cuz we'll bring them. So you can take a look. That's all thanks! Todd Tomlinson, great job on the focus.

A

That does it for the meeting we usually open up for general discussion, if you guys have anything in particular, you would like to bring up to talk about regarding the release or anything else.

A

No nothing all right: okay, well, yeah go team hits release day, it's really exciting, I'm, reiterating with the amounts and volume and honestly the thing that most it. What's that the quality, the quality yeah and honestly, the thing that I'm most excited about is the treatment that we've had of other people like we've, had a lot of new people come in like right here at the last second as well, and it's been just fantastic collaboration across the board like lots of great welcomes and congratulations and high-fives and lots of great enthusiasm.

A

It's it's been great because I'm sure that you know, even though this is free, open source and we're doing this, because we we want to- and we like it, it's just great to see that passion channeled into excitement, rather than into like you know, fury so I've been really happy with the with our entire community in the way that we've been treating each other under a stressful situation. So yay very excited.

A

Never calls that.

A

Okay, all right! Well, thank you, everybody for joining the meeting and thank you everybody for watching. We will be collaborating.

B

Together at github and.

A

Get ur and let's finish this thing.

B

Can you ruin see.

A

You guys next week.