Dev meeting 2016 03 01

Agenda

• Issues needing escalation
• 2.2 branch
  • Should we declare a block on feature additions
  • Should we allow features in 2.x and resume 2.x minor releases, but keep 2.2.x as LTS
  • If we're going to do minor feature additions in 2.x, put them in a 2.3 & 2.4 … but (potentially) follow Symfony's model and keep 2.2 as LTS, just closed to features
  • 2.x branches would (obviously) stay 5.3.3 compat too
  • Obviously the "against" would be how that will impact the development team's spread
  • We're close to v3… so maybe just declare 2.2 bugfix only… EoS
• Doing weekly or twice-a-week blogposts on Bolt.cm, ramping up to the 3.0.0 release. Subjects:
  • Why did we decide to refactor a bunch of things? (SRP, testability, extensibility, etc)
  • New Storage layer
  • New Extensions structure
  • Repeater fields
  • Backend UI refresh
  • Widgets
  • Refactored sessions
  • Improved tests / code coverage
  • Improved Javascipt backend code
  • New base theme
  • New docs
  • New controller & routing layer
  • Web asset queues
  • (I'm positive i've forgotten some important parts.. Please add)

Log

<gawainlynch> ping Bopp carsonfull gawainlynch ('cause I can) phillipp rossriley SahAssar slick0 … rarila in absentia
<gawainlynch> Arguing on Slack!
<phillipp> here
<rossriley> present
<SahAssar> I said a hip hop the hippie the hippie to the hip hip hop, a you dont stop
<Bopp> pong
<phillipp> ah sahassar is grooving in
<gawainlynch> OK… lets get moving
<gawainlynch> 2.2 branch… Should we declare a block on feature additions or should we revert to minor releases that follow BC?
<rossriley> yes
<Bopp> yes.
<gawainlynch> Is that for a) or b) you two?
<rossriley> to the first part
<gawainlynch> Bopp: ?
<phillipp> so backporting some bolt 3 features? yes i am for that :)
<SahAssar> No new features.
<Bopp> My gut feeling is: feature freeze on 2.2, no more minors in 2.x 
<gawainlynch> OK done
<Bopp> backporting is nice, but it takes up resources that could flow into 3.x!
<gawainlynch> Bopp: Want to take the lead on the blog posts please
<phillipp> yeah true Bopp
<Bopp> Yes, blog posts. 
<Bopp> I want to start posting blog posts on bolt.cm regularly. perhaps twice a week on fridays / tuesdays.
<Bopp> ramping up to the bolt 3.0.0 release, 
<Bopp> in which we post about all the cool new stuff. 
<phillipp> nice
<Bopp> we'll get a bit of hype going, 
<[BoltGitHubBot]> [bolt] GawainLynch closed issue #4652: Improve deprecation handling for controllers. https://git.io/vukNS
<Bopp> and at the same time, it'll be an extra tool to check if the docs are up to speed, and such. 
<phillipp> so a blog post for each new feature would be cool
<Bopp> There's a list here: https://github.com/bolt/bolt/wiki/Dev-meeting-2016-03-01\
<Bopp> but, I'm probably missing some things still 
<Bopp> Anyhow, I'm going to set up the schedule and stuff. 
* Twiebie has quit (Ping timeout: 264 seconds)
<Bopp> But, I could use some help writing a few of them.. Both for time, as well as some of the more technical ones, that i'm just not knowledgeable enough on, just yet
<phillipp> Bopp: could we also blog about some useful extensions there? (maybe i could do that) then i can move a bit back from Medium too
<Bopp> I'll set up the schedule, and then i'll start soliciting help! :-)
<gawainlynch> Bopp: It would be good if someone could interview members of the core team too
<Bopp> phillipp: Awesome idea! 
<gawainlynch> Get a feel for the "inside view" of the changes
<Bopp> gawainlynch: Yes, that too!
<gawainlynch> phillipp: +1
<phillipp> uhh interviews! :P
<Bopp> In short: let's do more with adding fresh content to the bolt.cm site
<SahAssar> Crossposting to both medium and the blog might be good
<gawainlynch> phillipp: More that it can be hard for the core team to find time to write, plus not all are writers… but what's in our head is valuable 
<phillipp> Bopp: and then you can setup my website account. you want to do that for ages xD
<Bopp> phillipp: Yes! going to do that after the meetup!
<phillipp> i ll remind you next week :D
<gawainlynch> rossriley: #4703 is that something that is still relevant?
-[BoltIssueBall]/#boltcms- #4703 [open] Repeater field problems https://github.com/bolt/bolt/issues/4703 
<gawainlynch> OK… so the outstanding "blocker" apart from that is sessions
<gawainlynch> https://github.com/bolt/bolt/compare/master...CarsonF:bugfix/sessions-and-csrf
* kbck has quit (Ping timeout: 248 seconds)
<gawainlynch> This branch is almost done… I am working with Carson (who is ending a sprint today) on the acceptance test failures
<Bopp> \0/ !!
* kbck (~kbck@87-205-53-16.adsl.inetia.pl) has joined #boltcms
<rossriley> gawainlynch: no I don’t think so
<gawainlynch> Minor crappy bug… but that should close 4 or 5 bugs
<gawainlynch> rossriley: Closeable?
<gawainlynch> ('cause I do Engrish!"
<gawainlynch> (and typing)
<rossriley> yes, a lot of parts have been simplified since that and I;ve not ome across any of the bugs inrecent testing
<gawainlynch> SahAssar: Kill with valor!
<Bopp> and a lot of "feeling of being unfinished" in the backend, when the notices for CSRF are gone
<gawainlynch> :-)
<gawainlynch> Yeah, not to mention clients that will be happy
<[BoltGitHubBot]> [bolt] SahAssar closed issue #4703: Repeater field problems https://git.io/v2PlR
<gawainlynch> OK… so last point… beta
<gawainlynch> Thoughts?
<Bopp> gawainlynch: I'd like to put a tiny bit more effort into looking over the "package.sh" script..
<phillipp> (we have "How to communicate with extension developers" in the agenda for weeks) <= just a note
<Bopp> when csrf is in and packaging works, i'd say we're due for beta.
<gawainlynch> Bopp: WFM
<Bopp> (i'm going to move that to "blogpost")
<Bopp> (if we have a writeup on that, we can easily point them somewhere.
<gawainlynch> OK… anyone have anything to raise?
<Bopp> Steady as she goes.
<phillipp> (we could mail all registered devs on the extension store)
<gawainlynch> ^
* kbck has quit (Ping timeout: 250 seconds)
<Bopp> (yes, but _after_ a bit of a guide / tutorial, and somewhat stable beta)
<rossriley> we should release beta on St Patrick’s day… then we can drink guiness :-)
<phillipp> (sure but my point was to reach as much devs as possible)
* kbck (~kbck@87-205-53-16.adsl.inetia.pl) has joined #boltcms
<Bopp> phillipp: I think we're on the same page here! :-)
<phillipp> good
<gawainlynch> rossriley: More often than not, I find it hard to not like your suggestions :-)
<gawainlynch> …and?
<rossriley> March 17th Beta then
<phillipp> so we could write a guide and point to the finished docs and mail it to the registered devs
<Bopp> 17th sounds fun
<Bopp> ^ yes
<gawainlynch> 5… 4… 3…