Send Phpmyadmin-devel mailing list submissions to
        phpmyadmin-devel@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
or, via email, send a message with subject or body 'help' to
        phpmyadmin-devel-request@lists.sourceforge.net

You can reach the person managing the list at
        phpmyadmin-devel-owner@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Phpmyadmin-devel digest..."


Today's Topics:

   1. Re: how to use Phpmyadmin 3.5.5 r1? (Dieter Adriaenssens)
   2. about my pull request 121 and Travis (Marc Delisle)
   3. Re: about my pull request 121 and Travis (Michal ?iha?)
   4. Re: about my pull request 121 and Travis (Rouslan Placella)
   5. Re: ready for 4.0.0-alpha1 ? (Marc Delisle)
   6. Re: ready for 4.0.0-alpha1 ? (Dieter Adriaenssens)
   7. Re: ready for 4.0.0-alpha1 ? (Rouslan Placella)
   8. Re: ready for 4.0.0-alpha1 ? (Marc Delisle)


----------------------------------------------------------------------

Message: 1
Date: Wed, 19 Dec 2012 11:48:01 +0100
From: Dieter Adriaenssens <dieter.adriaenssens@gmail.com>
Subject: Re: [Phpmyadmin-devel] how to use Phpmyadmin 3.5.5 r1?
To: Jide Fowotade <jide_tade@yahoo.com>,
        phpmyadmin-devel@lists.sourceforge.net
Message-ID:
        <CAHXe6w4iAxaWSNUVsp8x3B_wMYe67WgBVZHcyqbzQ-M_HovpTg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

2012/12/19 Jide Fowotade <jide_tade@yahoo.com>:
> Hello everyone...
>
> I just downloaded the new phpmyadmin 3.5.5 r1 english, then i added it to
> the xampp folder
>
> but when i load the "localhost/xampp" on my browser it brings out a new
> security page. and says acces denied, that i have to configure something in
> the http-xampp.conf file.
>
> Would very much appreciate your help.

Hi,

This is clearly a XAMPP issue, not a phpMyAdmin issue. Please refer to
the XAMPP documentation or contact the XAMPP community for support.

--
Kind regards,

Dieter Adriaenssens

------------------------------

Message: 2
Date: Wed, 19 Dec 2012 06:22:34 -0500
From: Marc Delisle <marc@infomarc.info>
Subject: [Phpmyadmin-devel] about my pull request 121 and Travis
To: phpmyadmin-devel@lists.sourceforge.net
Message-ID: <50D1A37A.7070401@infomarc.info>
Content-Type: text/plain; charset=ISO-8859-1

Hi,
any objections to merge this? [0]. Well, Travis complains but I don't
understand why.

[0] https://github.com/phpmyadmin/phpmyadmin/pull/121

--
Marc Delisle
http://infomarc.info



------------------------------

Message: 3
Date: Wed, 19 Dec 2012 12:49:54 +0100
From: Michal ?iha? <michal@cihar.com>
Subject: Re: [Phpmyadmin-devel] about my pull request 121 and Travis
To: phpmyadmin-devel@lists.sourceforge.net
Message-ID: <20121219124954.364f7ba2@rincewind.suse.cz>
Content-Type: text/plain; charset="utf-8"

Hi

Dne Wed, 19 Dec 2012 06:22:34 -0500
Marc Delisle <marc@infomarc.info> napsal(a):

> any objections to merge this? [0]. Well, Travis complains but I don't
> understand why.

Travis recently complains quite a lot on too long time git clone takes,
nothing we could solve...

--
        Michal ?iha? | http://cihar.com | http://blog.cihar.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available

------------------------------

Message: 4
Date: Wed, 19 Dec 2012 11:48:12 +0000
From: Rouslan Placella <rouslan@placella.com>
Subject: Re: [Phpmyadmin-devel] about my pull request 121 and Travis
To: phpmyadmin-devel@lists.sourceforge.net
Message-ID: <50D1A97C.3000908@placella.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 12/19/2012 11:22 AM, Marc Delisle wrote:
> Hi,
> any objections to merge this? [0]. Well, Travis complains but I don't
> understand why.
>
> [0] https://github.com/phpmyadmin/phpmyadmin/pull/121
>

Travis is failing because it isn't managing to clone from github...

As far as pull request goes, I don't like the fact that you are hiding
the #page_content element (I'd wrap and hide its contents), but this is
no grounds for objecting the merge. So I guess that it's fine by me.

Bye,
Rouslan



------------------------------

Message: 5
Date: Wed, 19 Dec 2012 08:26:21 -0500
From: Marc Delisle <marc@infomarc.info>
Subject: Re: [Phpmyadmin-devel] ready for 4.0.0-alpha1 ?
To: phpmyadmin-devel@lists.sourceforge.net
Message-ID: <50D1C07D.9080303@infomarc.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Rouslan Placella a ?crit :
> On 12/13/2012 05:44 PM, Marc Delisle wrote:
>> Hi,
>>
>> Let's discuss an alpha version for 4.0. In the bug tracker, I tried to
>> find issues that are serious enough to block releasing the first alpha
>> version, and could not find any.
>>
>> Opinions?
>>
>
> The server status monitor pages still need some work, I have a branch
> with a whole bunch of fixes[0] that I intend to merge some time soon.
> Even after I do so, there will still be a few more bugs in those pages,
> all old and untracked, including a show-stopper in the localStorage
> feature. I'll file them as soon as I get a chance on the tracker.

The split-server-status branch has been merged, the localStorage feature
has been fixed.

Anything else that would be a showstopper for an alpha1 ?

--
Marc Delisle
http://infomarc.info



------------------------------

Message: 6
Date: Wed, 19 Dec 2012 14:51:22 +0100
From: Dieter Adriaenssens <dieter.adriaenssens@gmail.com>
Subject: Re: [Phpmyadmin-devel] ready for 4.0.0-alpha1 ?
To: phpmyadmin-devel@lists.sourceforge.net
Message-ID:
        <CAHXe6w6joHUFJms66_6x0DtP=KVB00tmybQXTcdd2m_M0d9hXA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

2012/12/19 Marc Delisle <marc@infomarc.info>:
> Rouslan Placella a ?crit :
>> On 12/13/2012 05:44 PM, Marc Delisle wrote:
>>> Hi,
>>>
>>> Let's discuss an alpha version for 4.0. In the bug tracker, I tried to
>>> find issues that are serious enough to block releasing the first alpha
>>> version, and could not find any.
>>>
>>> Opinions?
>>>
>>
>> The server status monitor pages still need some work, I have a branch
>> with a whole bunch of fixes[0] that I intend to merge some time soon.
>> Even after I do so, there will still be a few more bugs in those pages,
>> all old and untracked, including a show-stopper in the localStorage
>> feature. I'll file them as soon as I get a chance on the tracker.
>
> The split-server-status branch has been merged, the localStorage feature
> has been fixed.
>
> Anything else that would be a showstopper for an alpha1 ?

Nothing I can think of at the moment.

This would mean we go into 'preparation for the next major release'
mode, which will mean a freeze on features and new translatable
strings [0].
Should we create a QA_4_0 branch  at this point, were all the
preparations for 4.0 go? Or will we wait with this branch until we go
into the release candidate stage?
How about code cleanup? Only in master or do we still allow it for
4.0-dev until the rc-stage.


[0] http://wiki.phpmyadmin.net/pma/Gettext_for_developers#Guidelines_on_adding.2Fupdating_messages_in_the_different_branches


--
Kind regards,

Dieter Adriaenssens



------------------------------

Message: 7
Date: Wed, 19 Dec 2012 13:38:35 +0000
From: Rouslan Placella <rouslan@placella.com>
Subject: Re: [Phpmyadmin-devel] ready for 4.0.0-alpha1 ?
To: phpmyadmin-devel@lists.sourceforge.net
Message-ID: <50D1C35B.6040700@placella.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 12/19/2012 01:26 PM, Marc Delisle wrote:
> Rouslan Placella a ?crit :
>> On 12/13/2012 05:44 PM, Marc Delisle wrote:
>>> Hi,
>>>
>>> Let's discuss an alpha version for 4.0. In the bug tracker, I tried to
>>> find issues that are serious enough to block releasing the first alpha
>>> version, and could not find any.
>>>
>>> Opinions?
>>>
>>
>> The server status monitor pages still need some work, I have a branch
>> with a whole bunch of fixes[0] that I intend to merge some time soon.
>> Even after I do so, there will still be a few more bugs in those pages,
>> all old and untracked, including a show-stopper in the localStorage
>> feature. I'll file them as soon as I get a chance on the tracker.
>
> The split-server-status branch has been merged, the localStorage feature
> has been fixed.
>
> Anything else that would be a showstopper for an alpha1 ?

Not a showstopper, but we have quite a few outdated third party js
libraries. It's probably a good idea to upgrade them before the alpha.
Here are a few:

codemirror 2.18 -> 3.0
jquery 1.6.2 -> 1.8.3
jquery ui 1.8.16 -> 1.9.2
jquery ui timepicker 0.9.6 -> 1.1.1
jquery qtip -> can be dropped after jquery ui is upgraded as it will
come with a tooltip plugin included

Bye,
Rouslan



------------------------------

Message: 8
Date: Wed, 19 Dec 2012 09:16:20 -0500
From: Marc Delisle <marc@infomarc.info>
Subject: Re: [Phpmyadmin-devel] ready for 4.0.0-alpha1 ?
To: phpmyadmin-devel@lists.sourceforge.net
Message-ID: <50D1CC34.6030806@infomarc.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Dieter Adriaenssens a ?crit :
> 2012/12/19 Marc Delisle <marc@infomarc.info>:
>> Rouslan Placella a ?crit :
>>> On 12/13/2012 05:44 PM, Marc Delisle wrote:
>>>> Hi,
>>>>
>>>> Let's discuss an alpha version for 4.0. In the bug tracker, I tried to
>>>> find issues that are serious enough to block releasing the first alpha
>>>> version, and could not find any.
>>>>
>>>> Opinions?
>>>>
>>> The server status monitor pages still need some work, I have a branch
>>> with a whole bunch of fixes[0] that I intend to merge some time soon.
>>> Even after I do so, there will still be a few more bugs in those pages,
>>> all old and untracked, including a show-stopper in the localStorage
>>> feature. I'll file them as soon as I get a chance on the tracker.
>> The split-server-status branch has been merged, the localStorage feature
>> has been fixed.
>>
>> Anything else that would be a showstopper for an alpha1 ?
>
> Nothing I can think of at the moment.
>
> This would mean we go into 'preparation for the next major release'
> mode, which will mean a freeze on features and new translatable
> strings [0].
> Should we create a QA_4_0 branch  at this point, were all the
> preparations for 4.0 go? Or will we wait with this branch until we go
> into the release candidate stage?

I suggest starting QA_4_0 at the 4.0.0-beta1 release.

> How about code cleanup? Only in master or do we still allow it for
> 4.0-dev until the rc-stage.

I would say, only during the alpha stage.

>
>
> [0] http://wiki.phpmyadmin.net/pma/Gettext_for_developers#Guidelines_on_adding.2Fupdating_messages_in_the_different_branches
>
>


--
Marc Delisle
http://infomarc.info



------------------------------

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d

------------------------------

_______________________________________________
Phpmyadmin-devel mailing list
Phpmyadmin-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel


End of Phpmyadmin-devel Digest, Vol 77, Issue 12
************************************************