Hi Usman
We still have a month until the release on February 6th. Any features or
bugs fixed before the Candidate build will be included in the final release.
On Wed, Dec 25, 2024 at 6:48 PM Usman Khan wrote:
> Hi,
> Will the 9.0 release include only the tasks completed in the current
> sprint(
Hi,
Will the 9.0 release include only the tasks completed in the current
sprint(Sprint 183), or will we manage a separate release tag to include
specific tasks that are part of the release?. I just want to go through any
new features or enhancements in the upcoming release.
Regards,
Usman Muzaffar
Can you describe a little about the workspace feature coming (I assume) in
9.0? Sounds exciting.
On Wed, Dec 18, 2024 at 9:18 AM Akshay Joshi
wrote:
> Hi Hackers,
>
> Due to the holiday season, the next scheduled release planned for January
> 9th, 2025, will be skipped. The next major version v9
Hi Anthony
The workspace layout offers distraction-free, dedicated areas for tools
such as the Query Tool, PSQL, and Schema Diff. The design has been updated
with a toolbar on the left side of pgAdmin, providing a separate workspace
for Query Tool, PSQL, and Schema Diff Tool. A Settings (Preferenc
Hi Hackers,
Due to the holiday season, the next scheduled release planned for January
9th, 2025, will be skipped. The next major version v9.0 will be released on
February 6th.
Akshay Joshi
Principle Software Architect
enterprisedb.com
* Blog*: https://www.enterprisedb.com/akshay-joshi
* Git
On Thu, Feb 15, 2018 at 2:26 PM, Robert Eckhardt
wrote:
> Apologies if this has been discussed and I missed it.
>
> When is the 3.0 release planned?
>
I was planning it to be in a week or two, however I'm currently dealing
with a family emergency so it's likely to be March now.
--
Dave Page
Bl
Apologies if this has been discussed and I missed it.
When is the 3.0 release planned?
-- Rob
On Fri, Nov 17, 2017 at 10:04 AM, Surinder Kumar <
surinder.ku...@enterprisedb.com> wrote:
> Hi
>
> On Fri, Nov 17, 2017 at 2:46 PM, Dave Page wrote:
>
>> Hi
>>
>> The entire point of this patch was to allow an older version of pgAdmin
>> to run against a newer version of the database without thr
Hi
On Fri, Nov 17, 2017 at 2:46 PM, Dave Page wrote:
> Hi
>
> The entire point of this patch was to allow an older version of pgAdmin to
> run against a newer version of the database without throwing errors like
> this. Of course, it'll only work if we're careful to ensure we don't make
> any ba
Hi
The entire point of this patch was to allow an older version of pgAdmin to
run against a newer version of the database without throwing errors like
this. Of course, it'll only work if we're careful to ensure we don't make
any backward-incompatible changes, but adding columns such as this change
Hi Dave,
There is no programmatic way of fixing the issue if you have already
deleted the new migration file without downgrading via alembic downgrade
command.
The only way I know is to manually update 'alembic_version' table in
pgAdmin4.db to current revision which is 'ef590e979b0d'
-- Murtuza
On Fri, Aug 25, 2017 at 9:34 AM, Dave Page wrote:
>
>
> On Fri, Aug 25, 2017 at 9:28 AM, Harshal Dhumal <
> harshal.dhu...@enterprisedb.com> wrote:
>
>> One more thing that this will only work for future pgAdmin4 versions
>>
>
>
> Yeah :-(
>
Hmm, can you check this please? I'm getting the error
Hi
On Fri, Aug 25, 2017 at 2:04 PM, Dave Page wrote:
>
>
> On Fri, Aug 25, 2017 at 9:28 AM, Harshal Dhumal <
> harshal.dhu...@enterprisedb.com> wrote:
>
>> One more thing that this will only work for future pgAdmin4 versions
>>
>
>
> Yeah :-(
>
>
>>
>> --
>> *Harshal Dhumal*
>> *Sr. Software Eng
On Fri, Aug 25, 2017 at 9:28 AM, Harshal Dhumal <
harshal.dhu...@enterprisedb.com> wrote:
> One more thing that this will only work for future pgAdmin4 versions
>
Yeah :-(
>
> --
> *Harshal Dhumal*
> *Sr. Software Engineer*
>
> EnterpriseDB India: http://www.enterprisedb.com
> The Enterprise P
One more thing that this will only work for future pgAdmin4 versions
--
*Harshal Dhumal*
*Sr. Software Engineer*
EnterpriseDB India: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Fri, Aug 25, 2017 at 1:48 PM, Dave Page wrote:
>
>
> On Fri, Aug 25, 2017 at 9:15 AM, Surinder
On Fri, Aug 25, 2017 at 9:15 AM, Surinder Kumar <
surinder.ku...@enterprisedb.com> wrote:
> Hi
>
> On Fri, Aug 25, 2017 at 12:21 PM, Ashesh Vashi <
> ashesh.va...@enterprisedb.com> wrote:
>
>> On Fri, Aug 25, 2017 at 12:16 PM, Surinder Kumar <
>> surinder.ku...@enterprisedb.com> wrote:
>>
>>> Hi
Hi
On Fri, Aug 25, 2017 at 12:21 PM, Ashesh Vashi <
ashesh.va...@enterprisedb.com> wrote:
> On Fri, Aug 25, 2017 at 12:16 PM, Surinder Kumar <
> surinder.ku...@enterprisedb.com> wrote:
>
>> Hi
>> On Fri, Aug 25, 2017 at 1:03 AM, Dave Page wrote:
>>
>>>
>>>
>>> On Thu, Aug 24, 2017 at 8:28 PM,
On Fri, Aug 25, 2017 at 12:16 PM, Surinder Kumar <
surinder.ku...@enterprisedb.com> wrote:
> Hi
> On Fri, Aug 25, 2017 at 1:03 AM, Dave Page wrote:
>
>>
>>
>> On Thu, Aug 24, 2017 at 8:28 PM, Harshal Dhumal <
>> harshal.dhu...@enterprisedb.com> wrote:
>>
>>>
>>>
>>> --
>>> *Harshal Dhumal*
>>> *S
Hi
On Fri, Aug 25, 2017 at 1:03 AM, Dave Page wrote:
>
>
> On Thu, Aug 24, 2017 at 8:28 PM, Harshal Dhumal <
> harshal.dhu...@enterprisedb.com> wrote:
>
>>
>>
>> --
>> *Harshal Dhumal*
>> *Sr. Software Engineer*
>>
>> EnterpriseDB India: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Co
On Thu, Aug 24, 2017 at 8:28 PM, Harshal Dhumal <
harshal.dhu...@enterprisedb.com> wrote:
>
>
> --
> *Harshal Dhumal*
> *Sr. Software Engineer*
>
> EnterpriseDB India: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
> On Thu, Aug 24, 2017 at 9:44 PM, Dave Page wrote:
>
>>
>>
>>
--
*Harshal Dhumal*
*Sr. Software Engineer*
EnterpriseDB India: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
On Thu, Aug 24, 2017 at 9:44 PM, Dave Page wrote:
>
>
> On Thu, Aug 24, 2017 at 10:36 AM, Surinder Kumar <
> surinder.ku...@enterprisedb.com> wrote:
>
>> Hi Dave,
>>
>>
On Thu, Aug 24, 2017 at 10:36 AM, Surinder Kumar <
surinder.ku...@enterprisedb.com> wrote:
> Hi Dave,
>
> On Thu, Aug 24, 2017 at 2:28 PM, Dave Page wrote:
>
>> Anyone object to doing a release on 14th September, wrapping the code on
>> Monday 11th? This seems like the best option for our QA folk
+1 to 2.0
--
Thanks,
Murtuza
On Thu, Aug 24, 2017 at 3:06 PM, Surinder Kumar <
surinder.ku...@enterprisedb.com> wrote:
> Hi Dave,
>
> On Thu, Aug 24, 2017 at 2:28 PM, Dave Page wrote:
>
>> Anyone object to doing a release on 14th September, wrapping the code on
>> Monday 11th? This seems like t
Hi Dave,
On Thu, Aug 24, 2017 at 2:28 PM, Dave Page wrote:
> Anyone object to doing a release on 14th September, wrapping the code on
> Monday 11th? This seems like the best option for our QA folks who will be
> off for EID somewhen in the two weeks before.
>
> Assuming not, should this be 1.7 o
Hi,
On Thu, 2017-08-24 at 09:58 +0100, Dave Page wrote:
> Assuming not, should this be 1.7 or 2.0?
>
> If we go with 2.0, it'll be for "safety" given the proposed changes to path
> management to allow both server and desktop modes to work out of the box on
> Linux.
+1 to 2.0.
Regards,
--
Devr
Anyone object to doing a release on 14th September, wrapping the code on
Monday 11th? This seems like the best option for our QA folks who will be
off for EID somewhen in the two weeks before.
Assuming not, should this be 1.7 or 2.0?
If we go with 2.0, it'll be for "safety" given the proposed cha
26 matches
Mail list logo
