5.0 update and a plea for help with PostgreSQL

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

5.0 update and a plea for help with PostgreSQL

Mark Côté-2
We are finally closing in on 5.0 after two release candidates.  There
are only three bugs blocking release of rc3.  One is a simple fix to
release notes, and another is about fixing our upgrade tests, which dkl
will be working on shortly.  Thanks to all who helped test our release
candidates.

The last is a bug in our PostGreSQL 8.x support:
https://bugzilla.mozilla.org/show_bug.cgi?id=1138417

mtyson from Red Hat looked at it but has been unable to come up with a
fix thus far.  None of the other core BMO developers have sufficient
experience with Postgres.  Is there anyone out there who could take a look?

The other option is to drop support for Postgres 8.  Although still
packaged in supported enterprise Linux systems like RHEL, the last
Postgres 8 release, 8.4, was EOLed by the Postgres team in July 2014.
If we aren't able to find a good fix for bug 1138417 by the time the
other blockers are fixed, we will seriously consider officially dropping
support for Postgres 8.x.

Mark

--
Mark Côté
Assistant Project Lead, Bugzilla
_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
Reply | Threaded
Open this post in threaded view
|

Re: 5.0 update and a plea for help with PostgreSQL

Frédéric Buclin
Le 25. 03. 15 19:48, Mark Côté a écrit :
> We are finally closing in on 5.0 after two release candidates.  There
> are only three bugs blocking release of rc3.

rc3 or 5.0 final??


> The other option is to drop support for Postgres 8.

Another option is to backout bug 936275 from 5.0 as it's only used to
sort flags in buglists. And then you could bump the minimum version of
Pg to 9.0 for Bugzilla 6.0.


LpSolit

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: 5.0 update and a plea for help with PostgreSQL

Jeff Fearn
In reply to this post by Mark Côté-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/26/2015 04:48 AM, Mark Côté wrote:
> We are finally closing in on 5.0 after two release candidates.  There are only three bugs blocking release of rc3.  One is a simple fix to release notes, and another is about fixing our upgrade tests, which dkl will
> be working on shortly.  Thanks to all who helped test our release candidates.
>
> The last is a bug in our PostGreSQL 8.x support: https://bugzilla.mozilla.org/show_bug.cgi?id=1138417
>
> mtyson from Red Hat looked at it but has been unable to come up with a fix thus far.  None of the other core BMO developers have sufficient experience with Postgres.  Is there anyone out there who could take a look?
>
> The other option is to drop support for Postgres 8.  Although still packaged in supported enterprise Linux systems like RHEL, the last Postgres 8 release, 8.4, was EOLed by the Postgres team in July 2014. If we aren't
> able to find a good fix for bug 1138417 by the time the other blockers are fixed, we will seriously consider officially dropping support for Postgres 8.x.

+1 for dropping support for Postgres 8.x. Anyone on RHEL/EPEL-6 can use the postgresql 9.2 software collection.

Cheers, Jeff.

- --
Jeff Fearn
Senior Software Engineer
PnT DevOps
Red Hat Asia Pacific Pty Ltd

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVEy9DAAoJELs3R4zxGZvK3/gH/368AjLgzM8qbtyNFiNWNQzJ
ZKdZR7r1K4FGSac95N56PH32DUFv+Uz6GPhs+gNK82zFyq+/bqDPlq51k/LK0/+6
IvGqETe/gINUWDYvnvUlyWhlVYPO+oOP5axCt4Tz3laWwEULHxJ2NOixS1PbGjMB
Hjj0Qnv8Iu0yi/NS4+61x92Sp7QVKBN4655zg113TY3yIKXFRRmS0KqtbyK4OyyQ
6TyAd9oDHLJ1EKbAv2/AymBH9cgWQ3jpXrg5MHnkP8qTLTrYyk8axRQLRYvEpvJz
4ZpLX4W2gc7/MIQndFE99cUEEH/9mn013ZGQvEYb/7opeS6faZ+Z/5Jj0P66tZQ=
=grFy
-----END PGP SIGNATURE-----
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: 5.0 update and a plea for help with PostgreSQL

Mark Côté
In reply to this post by Mark Côté-2
On 2015-03-25 2:57 PM, Frédéric Buclin wrote:
> Le 25. 03. 15 19:48, Mark Côté a écrit :
>> We are finally closing in on 5.0 after two release candidates.  There
>> are only three bugs blocking release of rc3.
>
> rc3 or 5.0 final??

I guess there are different definitions of "release candidate"; I was
going by the literal definition, meaning rc3 would be a candidate for
general release.  If after a couple weeks no blockers are raised, rc3
would be (re)released as 5.0.

>> The other option is to drop support for Postgres 8.
>
> Another option is to backout bug 936275 from 5.0 as it's only used to
> sort flags in buglists. And then you could bump the minimum version of
> Pg to 9.0 for Bugzilla 6.0.

Yeah that's an option.  It comes down to whether advance notice of 6
months or so would make a difference to any sites still running 8.x.
Bug 936275 definitely isn't a critical issue.

Mark

_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
Reply | Threaded
Open this post in threaded view
|

Re: 5.0 update and a plea for help with PostgreSQL

Dave Lawrence
Ok. So lets just back out 936275. Release rc3 soon as possible. Then I will continue to work on the testing
and when that is done, if no issues have come up, we will release 5.0?

Sounds good to me.
dkl

On Wed, Mar 25, 2015 at 11:30 PM, Mark Côté <[hidden email]> wrote:
On 2015-03-25 2:57 PM, Frédéric Buclin wrote:
> Le 25. 03. 15 19:48, Mark Côté a écrit :
>> We are finally closing in on 5.0 after two release candidates.  There
>> are only three bugs blocking release of rc3.
>
> rc3 or 5.0 final??

I guess there are different definitions of "release candidate"; I was
going by the literal definition, meaning rc3 would be a candidate for
general release.  If after a couple weeks no blockers are raised, rc3
would be (re)released as 5.0.

>> The other option is to drop support for Postgres 8.
>
> Another option is to backout bug 936275 from 5.0 as it's only used to
> sort flags in buglists. And then you could bump the minimum version of
> Pg to 9.0 for Bugzilla 6.0.

Yeah that's an option.  It comes down to whether advance notice of 6
months or so would make a difference to any sites still running 8.x.
Bug 936275 definitely isn't a critical issue.

Mark

_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>



--
Reply | Threaded
Open this post in threaded view
|

Re: 5.0 update and a plea for help with PostgreSQL

Mark Côté-2
In reply to this post by Mark Côté
Works for me!

Mark


On 2015-03-26 3:10 PM, Dave Lawrence wrote:

> Ok. So lets just back out 936275. Release rc3 soon as possible. Then I will
> continue to work on the testing
> and when that is done, if no issues have come up, we will release 5.0?
>
> Sounds good to me.
> dkl
>
> On Wed, Mar 25, 2015 at 11:30 PM, Mark Côté <[hidden email]> wrote:
>
>> On 2015-03-25 2:57 PM, Frédéric Buclin wrote:
>>> Le 25. 03. 15 19:48, Mark Côté a écrit :
>>>> We are finally closing in on 5.0 after two release candidates.  There
>>>> are only three bugs blocking release of rc3.
>>>
>>> rc3 or 5.0 final??
>>
>> I guess there are different definitions of "release candidate"; I was
>> going by the literal definition, meaning rc3 would be a candidate for
>> general release.  If after a couple weeks no blockers are raised, rc3
>> would be (re)released as 5.0.
>>
>>>> The other option is to drop support for Postgres 8.
>>>
>>> Another option is to backout bug 936275 from 5.0 as it's only used to
>>> sort flags in buglists. And then you could bump the minimum version of
>>> Pg to 9.0 for Bugzilla 6.0.
>>
>> Yeah that's an option.  It comes down to whether advance notice of 6
>> months or so would make a difference to any sites still running 8.x.
>> Bug 936275 definitely isn't a critical issue.
>>
>> Mark
>>
>> _______________________________________________
>> dev-apps-bugzilla mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-apps-bugzilla
>> -
>> To view or change your list settings, click here:
>> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@...>
>>
>
>
>


--
Mark Côté
Assistant Project Lead, Bugzilla
_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>