Dev meeting 2017 09 05

Agenda

• 3.4.0 beta (@GawainLynch)
  • milestone 3.4 / Blocking issues

e.g.

• Status on drop bear invasion (@YourGitHubID)

Actionable Items

Outcomes

Log

19:30] 
gawainlynch
ping @bob @lenvanessen @sahassar @ross


[19:31] 
ross gnop


[19:31] 
sahassar
Pong


[19:31] 
lenvanessen Ola


[19:32] 
gawainlynch
OK, apologies from Carson … he's enjoying beaches and vacation weather (we hope)


[19:33] 
@ross: You make any more progress on that stuff we were going over?


[19:33] 
ross yes, I updated the PR for you to look at


[19:33] 
gawainlynch
Did you push?


[19:34] 
The last one I have is "nitpick"


[19:34] 
bob
sorry, pong!


[19:34] 
ross https://github.com/bolt/bolt/pull/6972/commits/8f471173efa234af4e9b5c25e3f2f6d318f278f0


[19:34] 
sorry, missed that step


[19:35] 
gawainlynch
Haha! :koala:


[19:36] 
OK … so I'll go over


[19:36] 
What I did want to raise was moving work onward to v4 attention


[19:37] 
Does anyone have nay good ideas on how we can best coordinate changes (i.e the PM) for v4 work? as I think it is fair to say "The time has come" (edited)


[19:38] 
bob
I think Gawain and I should coordinate on how to split up backend and frontend work


[19:39] 
and I will then work on the basis for the "frontend of the backend", hopefully with @jmarsh


[19:39] 
gawainlynch
Yeah, I am going to pretty much drop work on v3 features stuff from 3.4's release, and focus on v4 stuff … there is too much unmovable stuff in v3 and we're only endlessly pissing people off


[19:40] 
@ross: What are your thoughts/plans on storage stuff with relations to next-gen? (edited)


[19:41] 
ross A lot will depend upon how smoothly the compat work goes now


[19:41] 
if it goes to plan then I'll mainly be deleting stuff for 4.0


[19:42] 
gawainlynch
OK, so you're going to want to keep some degree of feature releases rolling for 3.x then?


[19:43] 
ross yes, not so much new features as moving over more stuff from legacy to new


[19:43] 
feature-wise I don't really have anything major in mind


[19:44] 
gawainlynch
OK, but will the changes be appropriate for 3.4.x+ as we go?


[19:44] 
ross yes


[19:44] 
bob
IMHO 3.3 (and soon 3.4) work pretty well.. We can keep using those, while working on the big 4.0


[19:44] 
gawainlynch
Yeah, part of what I want to try and get some PM around too, is that there is a tonne of old stuff that has just got to go, but my mind is still on how to provide some degree of transition


[19:46] 
bob
I think we all agree that after 3.4 our main focus should be 4.0


[19:47] 
gawainlynch
Oh yeah, sure … it is just how to we not make 4.0.0 too big of a bandaid to "rip off" to upgrade


[19:47] 
But we just need to get really serious about not breaking BC on people


[19:48] 
bob
How about we flip it around? Just thinking out loud here..


[19:48] 
gawainlynch
:ear: (edited)


[19:48] 
bob
We work on 4.0.. Do what we need to do.


[19:48] 
while we do that, we keep adding more "warnings" or "decprecation" notices to 3.x


[19:49] 
not unlike symfony did with 2.8 and 3.0


[19:49] 
gawainlynch
That is the current status quo :wink:


[19:49] 
bob
that way _upgrading_ to the latest 3.x should be fairly painless, and you'd get a good idea for what you can expect when updating to 4.0


[19:49] 
gawainlynch
But you have to add the stuff to 3.x (as SF did with 2.7 & 2.8)


[19:50] 
bob
yes, but so far we try to keep it _compatible_.


[19:50] 
Perhaps just say "Note: this will break, come 4.0" ?


[19:50] 
I'm not sure how that would work in practice, though


[19:51] 
gawainlynch
Well, you have to keep it to some extent, or provide the future alternative


[19:51] 
bob
Regardless, the path forward is 4.0, i think


[19:54] 
gawainlynch
@ross Is it fair to say then with your work, you're just interested in getting the storage transition across the line before touching v4?


[19:54] 
bob
Ok, is there more to add, for now? Or keep working on 3.4 and keep this goal for 4.0 in mind? :slightly_smiling_face:


[19:54] 
(sorry, tiny bit impatient)


[19:55] 
gawainlynch
Well, I just want to get the PM and direction somewhat laid out, Bob :slightly_smiling_face:


[19:55] 
If you need to go, catch up in the morning … zero stress


[19:55] 
ross yes I think so, there's a few features that can be built on the back of everyone having moved to the new engine


[19:55] 
so that's the big job ahead now


[19:55] 
gawainlynch
Yeah, I am gathering


[19:55] 
How can I help you?


[19:56] 
… or should I help you :smile:


[19:56] 
(i.e trying to help not hinder)


[19:59] 
@sahassar While waiting, are you aiming to carve out work space for 4.0?


[19:59] 
bob
Judging by the photo in #general, I think @sahassar is outside, and not paying attention to the meeting. :slightly_smiling_face:


[20:00] 
gawainlynch
Oh right, forgot


[20:00] 
sahassar
Here, and outside :)


[20:00] 
bob
Beers at WarPigs even perhaps, if my eyes don't deceive me.


[20:00] 
gawainlynch
Schrödinger's Meeting (edited)


[20:01] 
gawainlynch
can never find the freaking umlaut


[20:02] 
lenvanessen Doesn’t know how to make text italic


[20:02] 
The race….


[20:02] 
Who will teach me first


[20:02] 
bob
@lenvanessen it's markdownish in here.. `_italic_`


[20:02] 
gawainlynch
That one is just a sentence that starts with /me


[20:02] 
lenvanessen _ bob has won_ (edited)


[20:02] 
gawainlynch
started this one with /me


[20:02] 
bob
</sidetrack>


[20:03] 
bob
looks sternly


[20:03] 
gawainlynch
ping @ross @sahassar :stuck_out_tongue:


[20:03] 
lenvanessen For 4.0 we will be happy to carve out some time btw


[20:03] 
Myself personally and some guys here at wirelab probaby as wel


[20:03] 
bob
Whoop!


[20:04] 
gawainlynch
@lenvanessen When Carson is back, I am going to have a chat with him about what madness we can rope you into


[20:04] 
It would be good to get you +plus up and running as seamlessly as possible


[20:04] 
lenvanessen We’ve got some designers, some developers, and we’re desperate to get a handle on our CMS choice, so we’ll probably be able to help out where possible:)


[20:05] 
gawainlynch
OK, we should think about coordinating a meet-and-greet in here at some point


[20:05] 
sahassar
I wanna finish drag and drop sorting, CT singletons and config restructure


[20:05] 
lenvanessen Gawain is gonna swoop us of our feet for choosing bolt if i’m correct, and we’ve done work on the PyroCMS core before, so i’d say we would redirect that efforts to bolt:)


[20:06] 
gawainlynch
@sahassar: How much of that do you want to aim where?


[20:06] 
sahassar
All of it everywhere :)


[20:06] 
gawainlynch
Haha!


[20:06] 
I mean target branches


[20:07] 
sahassar
Sorry, don't really know right now, and can't check


[20:07] 
gawainlynch
FWIW I am very seriously thinking that I'll just target 4.0 with config … but I am willing to negotiate


[20:07] 
@sahassar No problems, when are you back?


[20:08] 
ross sorry, @gawainlynch missed your follow up


[20:08] 
gawainlynch
@ross: Mainly interested in helping is all, just don't want you to feel I am stepping on toes, or causing you *more* work


[20:10] 
ross I guess, keeping a check on whether approaches I'm using are good, and that we're not going to inconvenience people too much when they switch over storage layers


[20:10] 
there's a few things that have to break, but I'm trying to keep it down to things that can reasonably be patched in half an hour or so


[20:10] 
but we don't want to launch 4.0 and no marketplace themes work anymore


[20:11] 
so getting that part right will be the challenge


[20:11] 
gawainlynch
When you say break, do you mean in terms of flicking the compat setting one way or the other?


[20:11] 
Or absolute


[20:12] 
bob
(sorry, all.. I have to nip out.. Will catch up later tonight)


[20:12] 
ross yes, by the time 4.0 launches, all the themes will need to have implemented the compat patches


[20:13] 
so that they work with both old/new layers... then when 4.0 is released and the old goes, then noone should notice a break


[20:13] 
gawainlynch
Right, but if a site is on 3.0 now and updates to 3.9.x they will be fine without change? It would only be the upgrade to 4.0 that would require them?


[20:13] 
ross yes, unless they switch that new flag on


[20:13] 
setcontent_legacy: false


[20:13] 
gawainlynch
Perfect … sounds like a deal


[20:14] 
OK, well lets pick all this up next week when everyone is here and not on vacation or festivals or pubs :wink:


[20:14] 
#meeting


[20:14] 
boltissueball </meeting> Failed parsing XML: 'hug' expected, No 'love' shown for bot. Program 'meeting' terminated.


[20:15] 
gawainlynch
@lenvanessen You were going to say something?


[20:15] 
lenvanessen I was gonna beat you to the point with the meeting


[20:15] 
`#meeting` that is


[20:15] 
boltissueball </meeting> Failed parsing XML: 'hug' expected, No 'love' shown for bot. Program 'meeting' terminated.