2015 10_Meeting
See also the 2015-10 Meeting IRC Log
Now that we have settled for a monthly bugfix release, I would prefer extra precautions for 4.5.1 (especially taking into account its 33 issues fixed). How about a bugfix freeze one week before the bugfix release? This would mean opening MAINT_4_5_1 on Oct 17 and convincing volunteers to look for regressions during the last week of the cycle.
--Lem9 00:14, 14 October 2015 (CEST)
Agreed
Starting on Dec. 1st we will have two contractors, so should we plan the work repartition? For example, who will handle security coordination?
--Lem9 00:57, 7 October 2015 (CEST)
Moved to the team mailing list and postponed until next month
Now that GSoC 2016 has been announced, do we wish to participate? If so, what kind of improvements are we looking for, taking into account what our contractors' will be doing until Summer 2016?
--Lem9 00:57, 7 October 2015 (CEST)
Yes, we would like to participate. There might not be as many feature request tasks as in times past due to our contract developers, but there is still work to be done. Ideas include the Error Reporting, Automated Testing, and the OOP/Refactoring projects. We may elect to save/hold feature requests for GSoC project as well.
This is related to https://github.com/phpmyadmin/phpmyadmin/issues/11507.
- Should we move "Sort by key" at the right of "Filter rows", possibly replacing Ascending/Descending with ASC/DESC?
- Apart from that, do you see a need to optimize space on this page?
--Lem9 01:12, 7 October 2015 (CEST)
There are already some pull requests for improvements to limit the use of vertical space; we'll work to make this a bit better. Marc will move the Sort key to the right of Filter rows; even though these aren't the same thing they're both related to display so they can go together.
See https://github.com/phpmyadmin/phpmyadmin/issues/11508.
--Lem9 13:59, 14 October 2015 (CEST)
udan will ask the Packagist people about a feature request where we can merge our repository with theirs; this seems to be the ideal solution. If that doesn't work out, we'll document for people to use ours.
- https://github.com/phpmyadmin/phpmyadmin/issues/6137 (edge case?)
- https://github.com/phpmyadmin/phpmyadmin/issues/6369 (out of scope for a UI-oriented software?)
- https://github.com/phpmyadmin/phpmyadmin/issues/6353 (asking to kill queries ran by another user?)
--Lem9 15:54, 13 October 2015 (CEST)
- 6137 Isaac will work on as it's mostly a documentation issue
- 6369 will close as it's out of the project scope
- 6353 will close as we have limited control over this
Popular destinations:
- Team meetings
- GSoC home
- Developer guidelines
- How to install on Debian and Ubuntu
- Issue and pull-request management
User resources: