| 1 |
It's "This is not a final release, and it does have known issues, |
| 2 |
including a crash bug". But it can be used with PHP 7.2 to start |
| 3 |
upgrading applications. |
| 4 |
|
| 5 |
Ok, I'll create the issue in the Bugzilla and let the maintainer decide. |
| 6 |
|
| 7 |
|
| 8 |
On 12/08/2017 03:51 PM, Michael Orlitzky wrote: |
| 9 |
> On 12/08/2017 07:06 AM, Alexey Eschenko wrote: |
| 10 |
>> Hi guys. |
| 11 |
>> |
| 12 |
>> Some time ago PHP 7.2 was released. To start working with it I was |
| 13 |
>> needed XDebug and it was released in "alpha" version: https://xdebug.org/ |
| 14 |
>> |
| 15 |
>> Is there any policy against version bumps for "alpha" versions or I can |
| 16 |
>> create the issue about dev-php/xdebug bump in the Bugzilla? |
| 17 |
>> |
| 18 |
> It's up to the maintainer... we have no policy against it, but you don't |
| 19 |
> want to commit broken/untested packages to the tree obviously. |
| 20 |
> |
| 21 |
> If the xdebug alpha is "we added php-7.2 support but haven't tested it |
| 22 |
> yet", then feel free to submit a normal version bump. On the other hand, |
| 23 |
> if it's "this new alpha version happens to support php-7.2 but also has |
| 24 |
> new features that might eat your server," then it would be better to add |
| 25 |
> it alongside a package.mask entry that says "masked for testing" or |
| 26 |
> something like that. |
| 27 |
> |
| 28 |
|
| 29 |
-- |
| 30 |
Kind regards, |
| 31 |
Alexey Eschenko |
| 32 |
https://skobk.in/ |
Archives