MySQL Bugs: #71993: OS support for MySQL 5.7 is undocumented

Bug #71993	OS support for MySQL 5.7 is undocumented
Submitted:	10 Mar 2014 11:20	Modified:	12 Mar 2014 16:37
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.7	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
This page/document http://www.mysql.com/support/supportedplatforms/database.html has no details for MySQL 5.7 versions.

How to repeat:
Read http://www.mysql.com/support/supportedplatforms/database.html.

Suggested fix:
Add details for MySQL 5.7.

Thank you for the bug report.

MySQL 5.7 is not yet GA, and it is not intended for production deployments, and is not fully "supported" such that it would be listed in that context.

I am sorry, but where is then the right context?  I want to try MySQL 5.7 and am looking for information whether it is supported and functional on my OS. 

I believe that this was closed because of *irritation* and not because of *rational thought*.  It is a valid request to ask for that kind documentation - also for beta releases. 

I will not accept the closure as 'not a bug' unless you point to another place where I can find the requested documentation/information. This is YAHE (yet another horrible example) a typical example of the arrogant attitude that seems to have become common among Oracle/MySQL developers over the latest years.

And formally/sematically: this page http://dev.mysql.com/doc/refman/5.7/en/supported-os.html (*what is for MySQL 5.7*) points to a web page where it is claimed that the information I reqe3ust can be found.  But it is not there.  At least maybe you would be able to understand that it is a documentation bug, when one page in documentation ponts to another with missing information?

Peter,

The most relevant information is whether or not we produce packages for a given platform during pre-GA stages, and that information is found on the download pages.  The page you reference has very specific meaning to "supported" - it's a contract of sorts which defines which platforms for which we're committing to producing packages, testing and fixing bugs against.  Pre-GA software simply doesn't have the same sort of "contract."

I'm far from irritated or intending to treat you with arrogance.  I recognize that an answer of, "see what downloads we produce for a pre-GA release" isn't the answer you are likely looking for, but it's the best I can provide right now.  I think you'll also find that the MySQL team eager to hear about bugs against any platform, formally supported or not (e.g., we fixed compilation problems related to ARM in 5.6.13).  So if the point of asking is, "can I open bug reports against this platform," the answer is, "please do" - even if we can't commit to fully supporting it.

I also understand the desire to know what platforms are targeted for support with 5.7; codifying this in a formal "supported platforms" page is simply not something we can commit to at this stage of development.

I agree with your assertion that the http://dev.mysql.com/doc/refman/5.7/en/supported-os.html documentation web page needs to have better information.

Please let me know whether that addresses your concerns.

OK .. I apologize.

But formally there is a docs page claiming that what information about what OS's are supported is available on a webpage - what it is not. This is a formal bug in docs.

The docs page could say something like:

"MySQL 5.7 is currently in development.  When it reaches GA stage it will be fully documented what OS's are supported and what packages will be available.  However currently it is expected to work on same recent OS's as MySQL 5.6 does - refer <page/> on that. Please report a bug if you experience a situation where this is not the case, and it will be decided if this will be fixed or if support for the specific environment will discontinue in 5.7"

I agree with your docs suggestion (thanks!).  Ideally, I'd like to see the supported platforms formally defined at RC stage, but a GA commitment is easy to make and fulfill.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly.