Re: [GD-DEVEL] pending gd-2.2.0 release

On Thu, Jun 2, 2016 at 5:34 PM, Pierre Joye <[email protected]> wrote:
> hi,
>
> On Fri, May 20, 2016 at 10:04 AM, Mike Frysinger <[email protected]> wrote:
>> On 18 May 2016 19:52, Mike Frysinger wrote:
>>> we've got more than enough fixes queued up in the tree now for a
>>> new release.  does anyone have anything they think should block
>>> it ?
>>
>> i've pushed it out now.  we can always do a 2.2.1 if things need
>> tweaking.
>>
>>> i'd like to get the website fixed so we can actually announce it,
>>> but that doesn't mean we have to wait.
>>
>> i've pushed updates to the website repo, but it still fails to sync
>> to the github.io site :(.
>> -mike
>
> There are a couple of things to be done for 2.2.0 or we can target
> them for 2.3.0.
>
> What would you prefer? I suppose we could have your current work as
> 2.2.0 relatively fast out. An alpha cannot hurt and can be done
> quickly already even if we add one thing or another before final.
>
> Also we need to release 2.1.2 with the couple of bugs fixes (security mainly).
>
> Are you on IRC btw? We are on freenode (#libgd), it could be easier to
> catch up :)

I see that "releases" have been done already. I take the blame for the
slow answers (been quite stressful lately).

This is a good thing, thanks :)

However it should be done in a slightly different way tho'.

We still need to fix 2.1 (some projects won't update to 2.2) soon, we
can also end it later this year.

Given that 2.2.0 and 2.2.1 is already released, we can hardly start to
add features at this stage, so yes, let focus on 2.3. Please create
issues for each of them so we can sync there.

The 2.3.0 will then focus on new features (just had a call with
Nathanael about some of them).

About the website update, I am fine to change but the current system
works and I do not have the time to migrate it.

Also right now it is broken, I suppose it is due to the key changes :/

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org