Hi,
The current state of 3.0 is quite encouraging. I suggest a round of testing this summer, followed by -alpha early August, -beta in late August, -rc1 in mid-September ... and we'll see depending on the feedback.
Marc
Hi Marc,
On Friday 6 June 2008 18:28, Marc Delisle wrote:
The current state of 3.0 is quite encouraging. I suggest a round of testing this summer, followed by -alpha early August, -beta in late August, -rc1 in mid-September ... and we'll see depending on the feedback.
From a distributor's point of view the following.
If the final 3.0 will be released after September we probably won't be able to ship it in the next Debian stable. That is not a problem in and of itself, however, it means that we need to security support the 2.11 branch for at least the period until the next stable release comes out + 1 year. That is our responsibility, but I was wondering whether you as upstream authors would be willing to provide some kind of security-only support for the 2.11 branch for some time period.
It might influence the decision on which version we would include in the next stable release.
cheers, Thijs
Thijs Kinkhorst schrieb:
Hi Marc,
On Friday 6 June 2008 18:28, Marc Delisle wrote:
The current state of 3.0 is quite encouraging. I suggest a round of testing this summer, followed by -alpha early August, -beta in late August, -rc1 in mid-September ... and we'll see depending on the feedback.
From a distributor's point of view the following.
If the final 3.0 will be released after September we probably won't be able to ship it in the next Debian stable. That is not a problem in and of itself, however, it means that we need to security support the 2.11 branch for at least the period until the next stable release comes out + 1 year. That is our responsibility, but I was wondering whether you as upstream authors would be willing to provide some kind of security-only support for the 2.11 branch for some time period.
2.11 will be supported even after 3.0 is released, this is already planned
i think this will last _AT MINIMUM_ 1 year after 3.0 is released
Hi
On Tue, 10 Jun 2008 23:26:53 +0200 Thijs Kinkhorst thijs@debian.org wrote:
If the final 3.0 will be released after September we probably won't be able to ship it in the next Debian stable. That is not a problem in and of itself, however, it means that we need to security support the 2.11 branch for at least the period until the next stable release comes out + 1 year. That is our responsibility, but I was wondering whether you as upstream authors would be willing to provide some kind of security-only support for the 2.11 branch for some time period.
It will get not only security fixes but also bugfixes, because it will be only version still supporting older PHP and MySQL versions. I think we talked about at least one year support for it.
It might influence the decision on which version we would include in the next stable release.
We have to stay with 2.11, 3.0 will be too late for Lenny if there won't be major changes in release schedule. I think there is no chance that phpMyAdmin 3.0 will be ready in mid of July 2008.
Thijs Kinkhorst a écrit :
Hi Marc,
On Friday 6 June 2008 18:28, Marc Delisle wrote:
The current state of 3.0 is quite encouraging. I suggest a round of testing this summer, followed by -alpha early August, -beta in late August, -rc1 in mid-September ... and we'll see depending on the feedback.
From a distributor's point of view the following.
If the final 3.0 will be released after September we probably won't be able to ship it in the next Debian stable. That is not a problem in and of itself, however, it means that we need to security support the 2.11 branch for at least the period until the next stable release comes out + 1 year. That is our responsibility, but I was wondering whether you as upstream authors would be willing to provide some kind of security-only support for the 2.11 branch for some time period.
It might influence the decision on which version we would include in the next stable release.
cheers, Thijs
phpMyAdmin 3.0 requires PHP 5.2 and MySQL 5.0 so phpMyAdmin 2.11 will be security-supported for some time, at least a year like Sebastian said.
Marc
Hi
On Fri, 06 Jun 2008 12:28:45 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
The current state of 3.0 is quite encouraging. I suggest a round of testing this summer, followed by -alpha early August, -beta in late August, -rc1 in mid-September ... and we'll see depending on the feedback.
I don't remember exact time frame for GSoC, but the last beta should be IMHO after both GSoC things are done and merged.
Michal Čihař schrieb:
Hi
On Fri, 06 Jun 2008 12:28:45 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
The current state of 3.0 is quite encouraging. I suggest a round of testing this summer, followed by -alpha early August, -beta in late August, -rc1 in mid-September ... and we'll see depending on the feedback.
I don't remember exact time frame for GSoC, but the last beta should be IMHO after both GSoC things are done and merged.
i did not heard anything from GSoC ... is there any source blog or something similar, what shows progress of this?
On Wed, 11 Jun 2008 11:43:54 +0200 Sebastian Mendel lists@sebastianmendel.de wrote:
i did not heard anything from GSoC ... is there any source blog or something similar, what shows progress of this?
Every week, report is sent to http://lists.mysql.com/soc
My student is still busy with school right now, so there is not much progress so far.
Michal Čihař schrieb:
On Wed, 11 Jun 2008 11:43:54 +0200 Sebastian Mendel lists@sebastianmendel.de wrote:
i did not heard anything from GSoC ... is there any source blog or something similar, what shows progress of this?
Every week, report is sent to http://lists.mysql.com/soc
oh, thanks
before asking stupid questions their:
Piotr Przybylski:
KEY ACCOMPLISHMENTS LAST WEEK
- no time so nothing except getting svn permissions to work
is he talking about PMA SVN access? did he requested or got granted access to SVN?
On Wed, 11 Jun 2008 12:17:10 +0200 Sebastian Mendel lists@sebastianmendel.de wrote:
Michal Čihař schrieb:
On Wed, 11 Jun 2008 11:43:54 +0200 Sebastian Mendel lists@sebastianmendel.de wrote:
i did not heard anything from GSoC ... is there any source blog or something similar, what shows progress of this?
Every week, report is sent to http://lists.mysql.com/soc
oh, thanks
before asking stupid questions their:
Piotr Przybylski:
KEY ACCOMPLISHMENTS LAST WEEK
- no time so nothing except getting svn permissions to work
is he talking about PMA SVN access? did he requested or got granted access to SVN?
No, he prefers to use own SVN repo for development.
Michal Čihař schrieb:
On Wed, 11 Jun 2008 12:17:10 +0200 Sebastian Mendel lists@sebastianmendel.de wrote:
Michal Čihař schrieb:
On Wed, 11 Jun 2008 11:43:54 +0200 Sebastian Mendel lists@sebastianmendel.de wrote:
i did not heard anything from GSoC ... is there any source blog or something similar, what shows progress of this?
Every week, report is sent to http://lists.mysql.com/soc
oh, thanks
before asking stupid questions their:
Piotr Przybylski:
KEY ACCOMPLISHMENTS LAST WEEK
- no time so nothing except getting svn permissions to work
is he talking about PMA SVN access? did he requested or got granted access to SVN?
No, he prefers to use own SVN repo for development.
where could this be accessed?
On Wed, 11 Jun 2008 12:26:12 +0200 Sebastian Mendel lists@sebastianmendel.de wrote:
where could this be accessed?
It should be later here: https://trac.nq.pl/pma/
Michal Čihař schrieb:
On Wed, 11 Jun 2008 11:43:54 +0200 Sebastian Mendel lists@sebastianmendel.de wrote:
i did not heard anything from GSoC ... is there any source blog or something similar, what shows progress of this?
Every week, report is sent to http://lists.mysql.com/soc
about Raj Kissu:
issn't he advised or granted to use a branch in PMA SVN?
(didn't find the mentioned download at http://code.kissu.org/)
Sebastian Mendel a écrit :
Michal Čihař schrieb:
On Wed, 11 Jun 2008 11:43:54 +0200 Sebastian Mendel lists@sebastianmendel.de wrote:
i did not heard anything from GSoC ... is there any source blog or something similar, what shows progress of this?
Every week, report is sent to http://lists.mysql.com/soc
about Raj Kissu:
issn't he advised or granted to use a branch in PMA SVN?
(didn't find the mentioned download at http://code.kissu.org/)
It's not clear yet how he wants to proceed but in his Week 2 report he said that he'll upload some code to his site next week.
Michal Čihař a écrit :
Hi
On Fri, 06 Jun 2008 12:28:45 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
The current state of 3.0 is quite encouraging. I suggest a round of testing this summer, followed by -alpha early August, -beta in late August, -rc1 in mid-September ... and we'll see depending on the feedback.
I don't remember exact time frame for GSoC, but the last beta should be IMHO after both GSoC things are done and merged.
Why? We can schedule a new feature for 3.1, for example. In fact I would prefer to schedule the GSoC features for 3.1, because "we" have enough testing to do on the current 3.0-dev this summer.
Marc
Marc Delisle a écrit :
Michal Čihař a écrit :
Hi
On Fri, 06 Jun 2008 12:28:45 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca wrote:
The current state of 3.0 is quite encouraging. I suggest a round of testing this summer, followed by -alpha early August, -beta in late August, -rc1 in mid-September ... and we'll see depending on the feedback.
I don't remember exact time frame for GSoC, but the last beta should be IMHO after both GSoC things are done and merged.
Why? We can schedule a new feature for 3.1, for example. In fact I would prefer to schedule the GSoC features for 3.1, because "we" have enough testing to do on the current 3.0-dev this summer.
Marc
Just to recap and to get more feedback: I think that the last bunch of new code that should be merged for 3.0 is the update for Swekey auth, which is due in a few days.
Then we can - declare a feature freeze - open QA_3.0 - ask translators for updates - switch trunk to 3.1
As I said I prefer to merge Google Summer of Code features (BLOB streaming and the new setup code) in 3.1.
Marc
Hi
Dne Thu, 31 Jul 2008 09:08:34 -0400 Marc Delisle Marc.Delisle@cegepsherbrooke.qc.ca napsal(a):
Just to recap and to get more feedback: I think that the last bunch of new code that should be merged for 3.0 is the update for Swekey auth, which is due in a few days.
Then we can
- declare a feature freeze
- open QA_3.0
- ask translators for updates
- switch trunk to 3.1
As I said I prefer to merge Google Summer of Code features (BLOB streaming and the new setup code) in 3.1.
Okay for me.
-
Marc Delisle -
Michal Čihař -
Sebastian Mendel -
Thijs Kinkhorst