Re: [BuildStream] 1.4 release timeline, targets and breaking changes

[Agustín Benito Bethencourt <agustin benito codethink co uk>]

Hi,

On Thursday, 1 November 2018 16:54:59 CET Angelos Evripiotis via BuildStream-list wrote:
> Hiya!
>
> Hopefully this guy isn’t too late to the 1.4 party (needs some design
> debate):
> https://gitlab.com/BuildStream/buildstream/issues/744
>
> Can I assume that because it made it into this 1.4 tracking issue that it’s
> officially welcome?
> https://gitlab.com/BuildStream/buildstream/issues/743

for each release there is a feature page on the website. In general everything that is specific to each 
release should be there (or linked), including the incompatibilities with previous releases. Javier 
highlighted back then that we could have done a better job in 1.2. We have an new opportunity in this release 
to demonstrate we listen to our users and include this documentation as part of the release.

It is not as easy as it might seem though. If we leave it for until the days prior to the release, when we 
are extremely busy, the result will be worse than if we take it in consideration ahead of time.

To me, the right way to approach this is from the roadmap, that is, since the beginning, considering a 
feature done only when the release notes/documentation is merged, including the impact on previous releases 
that users need to be aware of. This would require to consider this kind of documentation part of the 
road-mapping. 

To answer your question, in my opinion #743 is not just welcome, it has to happen.

Best Regards 

-- 
Agustín Benito Bethencourt
Principal Consultant
Codethink Ltd
We respect your privacy.   See https://www.codethink.co.uk/privacy.html