Re: [Mageia-dev] MariaDB: problem: final estimated release date
> Colin Guthrie wrote: [...] > As a matter of fact, I've noticed lately Mandriva issuing updates to newer > versions of mysql for non-security reasons. Apparently they make > an exception to the no version updates policy for this package now > (obviously they keep the updates within the same stable branch). Perhaps > we could too for mariadb. Not saying we definitely should, I don't follow > mysql/mariadb development. > > well, it's more that the rc release will not be supported and the GA release will only contain bugfixes in difference to rc... if they are security related or cricital, that's to be seen at the time... but mysql/mariadb versioning is a bit odd... they consider that after the Beta release no new features will be included into the same branch (ie: 5.5) iow, all new versions greater than 5.5.21 in the 5.5 branch are bugfix releases...
Re: [Mageia-dev] MariaDB: problem: final estimated release date
Colin Guthrie wrote: > 'Twas brillig, and Maarten Vanraes at 23/03/12 17:39 did gyre and gimble: >> ( see https://mariadb.atlassian.net/secure/Dashboard.jspa , look at road map >> ) >> >> MariaDB RC 5.5.2229/Mar/12 >> MariaDB GA 5.5.2309/Apr/12 >> >> that means that the GA (final release) is 2 days after release freeze :-( >> (not counting any possible extra delays) >> >> however, i would like to have the final release and not the release >> candidate. >> >> any thoughts on this? > > Well, sh1t happens... We'll just have to go with the RC and we can > always issue an update to the final release afterwards. I don't think > this is a huge problem. If there happen to be delays for other reasons > we can maybe push it in, but I wouldn't bank on it! > > Col As a matter of fact, I've noticed lately Mandriva issuing updates to newer versions of mysql for non-security reasons. Apparently they make an exception to the no version updates policy for this package now (obviously they keep the updates within the same stable branch). Perhaps we could too for mariadb. Not saying we definitely should, I don't follow mysql/mariadb development.
Re: [Mageia-dev] MariaDB: problem: final estimated release date
'Twas brillig, and Maarten Vanraes at 23/03/12 17:39 did gyre and gimble: > ( see https://mariadb.atlassian.net/secure/Dashboard.jspa , look at road map ) > > MariaDB RC 5.5.22 29/Mar/12 > MariaDB GA 5.5.23 09/Apr/12 > > that means that the GA (final release) is 2 days after release freeze :-( > (not counting any possible extra delays) > > however, i would like to have the final release and not the release candidate. > > any thoughts on this? Well, sh1t happens... We'll just have to go with the RC and we can always issue an update to the final release afterwards. I don't think this is a huge problem. If there happen to be delays for other reasons we can maybe push it in, but I wouldn't bank on it! Col -- Colin Guthrie colin(at)mageia.org http://colin.guthr.ie/ Day Job: Tribalogic Limited http://www.tribalogic.net/ Open Source: Mageia Contributor http://www.mageia.org/ PulseAudio Hacker http://www.pulseaudio.org/ Trac Hacker http://trac.edgewall.org/
[Mageia-dev] MariaDB: problem: final estimated release date
( see https://mariadb.atlassian.net/secure/Dashboard.jspa , look at road map ) MariaDB RC 5.5.22 29/Mar/12 MariaDB GA 5.5.23 09/Apr/12 that means that the GA (final release) is 2 days after release freeze :-( (not counting any possible extra delays) however, i would like to have the final release and not the release candidate. any thoughts on this?
