Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Release planning

(we have been having some discussion on mattermost[1] about this)

I vote +1 to the every 6 months. As always if a significant feature
comes along (like more improvements to C++14) we can revise the
release plan to get these improvements into user's hands sooner.

Jonah Graham
Kichwa Coders Ltd.

On 16 May 2017 at 16:17, Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> wrote:
> BTW, when I say release every 6 months, I mean minor release where we are
> allowed to add functionality and APIs.
> From: <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer
> <dschaefer@xxxxxxxxxxxxxx>
> Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
> Date: Tuesday, May 16, 2017 at 11:14 AM
> To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
> Subject: [cdt-dev] Release planning
> Hey gang,
> I’m just looking ahead on how to manage releases for the next while and
> would like your thoughts on it.
> I have always thought releasing every three months just didn’t give us
> enough time to get the job done right, especially over the summer months. I
> think our Oxygen plan where we skipped Neon.3 really helped us focus.
> As a result, I’d like us to continue with a 6 month release cycle. That
> would make 9.4 in December for Oxygen.2, and 9.5 for Photon next June and so
> on.
> We can do maintenance releases any time and it probably makes sense to at
> least do ones for the .1 and .3 Eclipse releases.
> Thoughts?
> Doug.
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit

Back to the top