Self introduction, and maintaining MySQL package

[Bjorn Munch]

Hello,

I have just submitted a request for rename of the package
community-mysql "back" to mysql-community:

https://bugzilla.redhat.com/show_bug.cgi?id=958131

See there for more details and rationale.

I'm sorry that this took somewhat longer than intended to get out, I
had some urgent tasks to attend do, such as getting the first
development release of MySQL 5.7 out the door and its source to
Launchpad. On the other hand. this also means we have already updated
the 5.6 package from the initial GA release 5.6.10 to 5.6.11.

Since I do not yet have a sponsor, I cannot upload to
fedorapeople.org. Also, Oracle does not have public web host usable
for ad-hoc uploads like this, so for the time being I have ulpoaded to
my private web page here:

http://home.online.no/~bjornmu/fedora/

Please excuse my ISP for thinking the file extension .rpm is music. :-)

I have also run a koji scratch build:

http://koji.fedoraproject.org/koji/taskinfo?taskID=5317300

I've had some in-house expert help for preparing the new source RPM
and spec file, but I will be responsible for keeping the Fedora
packages up-to-date going forward. I have just ordered a laptop on
which I will install F18 for this purpose :-) . Development/testing is
also being done on a VM in our development lab running Rawhide.

About myself:

I waw at Sun since they acquired the small database startup I worked
for in 2002. When Sun acquired MySQL in 2008, I was working with
Release Engineering of PostgreSQL in Sun's own database group; I was
responsible for integrating PostgreSQL 8.3 into OpenSolaris.

After Sun scaled down its PostgreSQL efforts (I still build Solaris
binaries for the PG community when they have new releases), I worked
for a few years on maintaining the test framework that comes with
MySQL, before I moved back to doing Release Engineering.

Now I'm part of the MySQL RE team which is responsible for building
and releasing MySQL and other associated products on all the platforms
we deliver for, plus we run the large in-house automated build and
test farm in the lab in Trondheim, Norway where I'm also located.

It took a little time to get this (and myself) ready but future
updates should come much faster.

Regards,

-- 
Bjorn Munch
MySQL Release Engineering
Trondheim, Norway

[Michael Schwendt]

On Tue, 30 Apr 2013 15:08:08 +0200, Bjorn Munch wrote:

>  Since I do not yet have a sponsor, I cannot upload to
>  fedorapeople.org.  
That is misinformation. Note the bottom of the following paragraph:

https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Up...

>  Regards,
>   
-- 
M

[Bjorn Munch]

On 01/05 11.58, Michael Schwendt wrote:
>  On Tue, 30 Apr 2013 15:08:08 +0200, Bjorn Munch wrote:
>  
>  > Since I do not yet have a sponsor, I cannot upload to
>  > fedorapeople.org. 
>  
>  That is misinformation. Note the bottom of the following paragraph:
>  
>
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Up...
I have registered on fedoraproject.org and added my ssh key but I
could not upload. I'm not quite sure what I needed to do and in which
order. It doesn't quite follow the normal pattern since I'm not adding
a *new* package, just offering to keep maintaining an existing one.

But since I do have an alternative place to upload I figured this was
not urgent.

- Bjorn Munch

[Honza Horak]

On 05/02/2013 09:07 AM, Bjorn Munch wrote:> On 01/05 11.58, Michael 
Schwendt wrote:
> > On Tue, 30 Apr 2013 15:08:08 +0200, Bjorn Munch wrote:
> >
> >> Since I do not yet have a sponsor, I cannot upload to
> >> fedorapeople.org.
> >
> > That is misinformation. Note the bottom of the following paragraph:
> >
> > 
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Up...
>  I have registered on fedoraproject.org and added my ssh key but I
>  could not upload. I'm not quite sure what I needed to do and in which
>  order. It doesn't quite follow the normal pattern since I'm not adding
>  a *new* package, just offering to keep maintaining an existing one. 
I'm really glad to see some real action from your part finally. Just 
generally, package renaming is more or less "new package process" + 
"retiring process" together, so you can safely follow new package 
guidelines..

>  I have just submitted a request for rename of the package
>  community-mysql "back" to mysql-community:
>  
However, I need to repeat that this could have some impact to choosing 
default package when asking for "mysql" name, as I've described at:
http://lists.fedoraproject.org/pipermail/devel/2013-April/181340.html

I admit that the example there is not very common case, but since there 
*is* at least one existing, I'd rather stick with less nice, but more 
safe name community-mysql. How can you ensure that there is not any 
other (potentially more common) use case where something similar can 
happen? Testing several common use cases where mysql-community works is 
not an argument for me, since yum is too complex for this.

One recent example -- I've found that perl-DBD-MySQL got build against 
community-mysql few weeks back, when the current builds of 
community-mysql and mariadb were already in the repo. Honestly, I don't 
have a clue how that could happen, but it was another proof for me, that 
we should take the safest way as we could. Fortunately, in this case 
removing mysql-devel and mysql-embedded-devel providers from 
community-mysql packages should work fine.

Regards,
Honza

[Bjorn Munch]

On 02/05 17.53, Honza Horak wrote:
>  
>  > I have just submitted a request for rename of the package
>  > community-mysql "back" to mysql-community:
>  >
>  
>  However, I need to repeat that this could have some impact to
>  choosing default package when asking for "mysql" name, as I've
>  described at:
>  http://lists.fedoraproject.org/pipermail/devel/2013-April/181340.html 
We have tried to reproduce this case here but we didn't get the wrong
behaviour you refer to even with the name mysql-community. I don't why
you are getting problems.

>  One recent example -- I've found that perl-DBD-MySQL got build
>  against community-mysql few weeks back, when the current builds of
>  community-mysql and mariadb were already in the repo. Honestly, I
>  don't have a clue how that could happen, but it was another proof
>  for me, that we should take the safest way as we could. Fortunately,
>  in this case removing mysql-devel and mysql-embedded-devel providers
>  from community-mysql packages should work fine. 
The new package removed those provides.

In any case, this problem is not an argument for community-mysql since
even that caused undesired behaviour; renaming to mysql-community
would not make any difference.

- Bjorn Munch

[Norvald H. Ryeng]

On Fri, 03 May 2013 12:43:33 +0200, Bjorn Munch <bjorn.munch(a)oracle.com&gt;  
wrote:

>  On 02/05 17.53, Honza Horak wrote:
> >
> > > I have just submitted a request for rename of the package
> > > community-mysql "back" to mysql-community:
> > >
> >
> > However, I need to repeat that this could have some impact to
> > choosing default package when asking for "mysql" name, as I've
> > described at:
> > http://lists.fedoraproject.org/pipermail/devel/2013-April/181340.html
>
>  We have tried to reproduce this case here but we didn't get the wrong
>  behaviour you refer to even with the name mysql-community. I don't why
>  you are getting problems. 
We've managed to reproduce it now. This is currently only an issue for two  
pacakges: mysqltuner and mysqludf_xql. If the user doesn't have MySQL or  
MariaDB installed, MySQL is chosen. If one of the servers are already  
installed, it is not replaced.

Please log this in the package review. Let's proceed with the rest of the  
review and look at renaming as a separate issue later.

Regards,

Norvald H. Ryeng

[James Hogarth]

>  Please log this in the package review. Let's proceed with the rest of the
>  review and look at renaming as a separate issue later.
>
>
>  
The current maintainers  of community-mysql  stated that their preference
was to wait for F20 for community-msql 5.6 a couple of weeks back given
that we are well past Feature Freeze, Branch, Alpha and only a few days off
the Translation Deadline...

If the renaming is to be left as a separate issue then what specifically is
left for F19?

[Norvald H. Ryeng]

On Fri, 03 May 2013 16:06:36 +0200, James Hogarth  
<james.hogarth(a)gmail.com&gt; wrote:

> >
> > Please log this in the package review. Let's proceed with the rest of  
> > the
> > review and look at renaming as a separate issue later.
> >
>  The current maintainers  of community-mysql  stated that their preference
>  was to wait for F20 for community-msql 5.6 a couple of weeks back given
>  that we are well past Feature Freeze, Branch, Alpha and only a few days  
>  off
>  the Translation Deadline...
>
>  If the renaming is to be left as a separate issue then what specifically  
>  is
>  left for F19? 
The current maintainers have stated that they don't intend to maintain the  
package much longer, and we've volunteered to maintain it. Exactly how and  
when a transition of maintainership is done is still not decided, but  
please at least review our first package submission.

We've been open about the intention to upgrade to 5.6 for months, but have  
respectfully waited to submit since the change of default has been  
difficult enough without introducing yet another variable into the  
equation. Now that the dust has settled and we seem to have a default  
selection that works, it's time to upgrade.

I see review requests on the list for new packages that people want into  
F19, so I don't see how it could be too late for upgrading an existing  
package.

Regards,

Norvald H. Ryeng

[Rahul Sundaram]

Hi


On Mon, May 6, 2013 at 4:13 AM, Norvald H. Ryeng  wrote:

>  I see review requests on the list for new packages that people want
> into
>  F19, so I don't see how it could be too late for upgrading an existing
>  package.
>  

I don't think it is too late to update MySQL but a new package isn't really
comparable.  If existing packages break in an update, that is far more
problematic than a completely new package that a user has to choose to
install.

Rahul

[Norvald H. Ryeng]

On Mon, 06 May 2013 16:42:43 +0200, Rahul Sundaram <metherid(a)gmail.com&gt;  
wrote:

>  Hi
>
>
>  On Mon, May 6, 2013 at 4:13 AM, Norvald H. Ryeng  wrote:
>
> > I see review requests on the list for new packages that people want into
> > F19, so I don't see how it could be too late for upgrading an existing
> > package.
>
>  I don't think it is too late to update MySQL but a new package isn't  
>  really
>  comparable.  If existing packages break in an update, that is far more
>  problematic than a completely new package that a user has to choose to
>  install. 
The existing mysql-* packages will be replaced by mariadb-* packages on  
upgrade, and mariadb-* will be the default when pulled in by dependencies.  
The community-mysql-* packages is something the user has to choose to  
install.

Regards,

Norvald H. Ryeng