Hi Denis,
My suggestion is that in the current version release process, when
planning to release a version, first determine the Time, Scope and
ReleaseManager. On this basis, we can add another work of documentation,
which is to determine which documents need to be written and who should
write them,instead of adding documents after all the work is done.
在 2020/3/13 上午12:49, Denis Magda 写道:
Igniters,
With the final 2.8 release steps checked out today by announcing the
version globally (congrats!), it's a proper time to consider and tweak our
release process, making completion of some phases more predictable and
aligned. I would like to dedicate this thread solely to changes related to
the documentation.
If to do a recap, Ignite 2.8 announcement went out of sync with the
publication of binaries, Maven and other artifacts because our technical
documentation was completed long after the vote had been closed.
We can easily eliminate such glitches for future releases if agree to start
a vote only if Ignite docs are ready and can be published the same day with
other release artifacts. If the docs are completed and available
internally while the vote goes then we can work on a release blog post
(referring to docs details) and announce the release the same day when the
binaries/docs availability.
Thoughts? Let's change the process ensuring that the vote can be started
only if technical documentation is ready to be released?
-
Denis
