[MDEV-4873] Tasks before 10.0.4-release Created: 2013-08-09  Updated: 2013-09-25  Resolved: 2013-09-25

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.4
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Sergei Petrunia Assignee: Sergei Petrunia
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-4865 Change related to --log option/variab... Closed
is blocked by MDEV-4866 Test case for bugfix #34750 is not me... Closed
is blocked by MDEV-4874 10.0.4 - make release notes Closed
is blocked by MDEV-4885 When performance schema is disabled, ... Closed

 Description   

This task will have as a subtasks all tasks that we intend to fix for 10.0.4 release. We are not using the "version" feature from Jira because we're unable to get a small list of tasks.

  • Failures of "upgrade" tests in buildbot are not a problem for this release (the failures are caused by InnoDB's inability to start on 5.1's datadir)
  • Currently, all failing tests in buildbot are random. There are two kind of failures
    • "big" tests fail due to timeout
    • replication test failures (it is suspected that the problem is in the tests, not in the features being tested)
  • sol10-64 fails to compile. Is this a problem for making packages (ask Wlad or Daniel)
  • It seems, we don't need a merge from 5.5. We don't need a merge from 10.0-base
  • Elena is going through 5.6 changelogs and checking if a feature was merged/non-merged or partially merged. ETA is Saturday.
    Upd by Elena:
    • Added a list of new features, found during the first iteration through the release notes ("Changes" sections), to MDEV-4874 (as a comment);
    • Filed noticed problems as bugs, linked it to this task;
    • Now will be going through "Bugfixes" sections, since the distribution of items between "Changes" and "Bugfixes" is rather arbitrary, ETA unknown yet

 Comments   
Comment by Elena Stepanova [ 2013-08-09 ]

>> [Check with Elena] Failures of "upgrade" tests in buildbot are not a problem for this release (the failures are caused by InnoDB's inability to start on 5.1's datadir)
If it's the problem with InnoDB: auto-extending data file, then yes, it's the same for 5.1 => 5.6, filed as a buildbot issue MDEV-4860

>> TODO: Do we need a merge from 5.5/10.0-base ?
Imho we can't merge 5.5 now. There is the bug http://bugs.mysql.com/bug.php?id=69623 ; for 5.5.32, Sanja pushed a workaround, and after the release it was reverted since we are going to merge a proper bugfix from MySQL 5.5.33. So, now 5.5 tree contains the bug without the fix – it's an intermediate version which should not be released. Either we need to merge MySQL 5.5.33 to 5.5 first, or release 10.0.4 with MariaDB 5.5.32.

Comment by Elena Stepanova [ 2013-08-09 ]

>> TODO: Check this list with Elena

I'm now going through ALL changes listed in MySQL 5.6.0 - 5.6.10 release notes, one by one (not bugfixes so far, just "changes" as classified in release notes). The result of it will be 4 lists:
1) found in 10.0;
2) not found in 10.0;
3) partially found in 10.0 (example: MDEV-4865);
4) unknown (it's mainly internal changes which don't have any obvious representation).

For list 1, I will try to check if there are test cases missing, will create bugs if they are, and will link them to this one.
List 2 will be sent to you after I have it, so you could take a look and see if there is something that should have been merged, but was not.
Items from list 3 I will file as bugs and will link them to this one.
Actions on list 4 will depend on the resulting list and the time that we have left.

Generated at Thu Feb 08 06:59:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.