+1 to Davor and JB's point.
The incubator stuff can certainly be done thoroughly after the board's
decision (if in favor).
Graduation aside, keeping up the cadence of the release would be better in
the product life cycle.
Perhaps a different thread altogether but I wanted to suggest if we can
I'd suggest to proceed with 0.4.0-incubating (as JB previously planned).
My reasoning: I don't think we'll be able to release a non-incubating
release next week, regardless of the Board's graduation decision. I think
it will take a while (more details to follow on a separate thread). On the
other
Hi,
Either way is fine for me too.
We discussed about the release schedule independently from the
graduation process, that's why 0.4.0-incubator was planned around today.
Regards
JB
On 12/13/2016 06:02 PM, Daniel Kulp wrote:
Hate to suggest this….
Assuming the Board OK’s the graduation
Update: we think we've knocked off all the 0.4.0-incubating blockers,
including postponing some. JB is going to start the release process soon!
On Sat, Dec 3, 2016 at 10:42 PM, Jean-Baptiste Onofré
wrote:
> Very good point Frances.
>
> Definitely something we have to do.
>
>
Very good point Frances.
Definitely something we have to do.
Regards
JB
On 12/04/2016 07:38 AM, Frances Perry wrote:
Sounds great, JB!
The major blocker in my opinion is to finish the polishing pass on the
quickstarts and example archetypes, so that users will have a great
experience trying