?
avatar mbabker
mbabker
7 Jun 2016

The 3.6.x branch contains code and features that were planned for the original 3.6 release. Given the change in schedule, this branch needs updating to reflect its planned status as 3.7. This includes:

  • Renaming the branch
  • Addressing open PRs against it so it can be archived - https://github.com/joomla/joomla-cms/labels/PR-3.6.x
  • Bumping the version number
  • Notifying me so that the Jenkins script for the nightly builds can be updated to produce correct packages

// @joomla/cms-maintainers

avatar mbabker mbabker - open - 7 Jun 2016
avatar brianteeman
brianteeman - comment - 7 Jun 2016

Not 100% as some things f from this branch were moves into staging

avatar mbabker
mbabker - comment - 7 Jun 2016

It'd be good to identify what from https://github.com/joomla/joomla-cms/compare/3.6.x was committed then.

avatar brianteeman
brianteeman - comment - 7 Jun 2016

Blame george

avatar wilsonge
wilsonge - comment - 7 Jun 2016

I merged staging back into 3.6.x back when i cherry-picked all the PR's - so that branch is absolutely fine. I'm not sure what to do for the best. I honestly have half a mind to leave the branch name and PR's and just bump the version number in the file and be done with it

avatar brianteeman brianteeman - change - 8 Jun 2016
Labels Added: ?
avatar brianteeman
brianteeman - comment - 27 Jun 2016

@wilsonge please do something or close this


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10748.

avatar wilsonge wilsonge - change - 27 Jun 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-06-27 22:01:08
Closed_By wilsonge
avatar wilsonge wilsonge - close - 27 Jun 2016

Add a Comment

Login with GitHub to post a comment