> >
> > Just one thought maybe we can enforce the process to achieve docs, maybe
> via pre-commit hooks/updating the `breeze release-management publish-docs`
> command. So that anytime there is something new published we also check the
> docs to achieve
.
>
Yep. That would be nice to archive the
+1 for the implementing the process, have little clue about the provider. :)
Thanks,
Utkarsh Sharma
On Sun, Oct 29, 2023 at 10:59 PM Pierre Jeambrun wrote:
>
> +1
>
> Le ven. 27 oct. 2023 à 19:16, Aritra Basu a
> écrit :
>
> > Sounds like a good time to set the process up. +1 from me as well.
Hey everyone,
Thank Bowrna :)
@Jarek Dream Team, Indeed.
@Amogh Sure, no problem, we can sync on Slack when you are back.
As Ryan mentioned, we need to be able to deal with two types of docs.
1. Docs that are published before 18 months, older docs.
2. Docs that are published somewhere between
Yep.Added a very short "context" chapter linking to the detailed docs and
explaining "MAJOR", "MINOR". "PATCH" numbers.
On Sun, Oct 29, 2023 at 6:42 PM Pierre Jeambrun
wrote:
> There is already a whole section about Semver in the README, maybe we can
> just link to it ?
>
> Le dim. 29 oct. 2023
Good numbers also for Public runners:
We had on average (excluding MSSQL which is a bit longer) - 5x 35 minutes
for "core change" PR on Public runers = 175 build minutes . Now we will
have 5x 23 on average (DB tests) + 1 x 10 minutes (non-DB tests) = 125
minutes. This is ~ 30 % improvements on
There is already a whole section about Semver in the README, maybe we can
just link to it ?
Le dim. 29 oct. 2023 à 18:36, Pierre Jeambrun a
écrit :
> I think this is a good idea. Speaking for myself, it wasn't clear to me
> until I got involved in the release process.
>
> In that PR, I think
I think this is a good idea. Speaking for myself, it wasn't clear to me
until I got involved in the release process.
In that PR, I think mentioning semver and pointing to the spec could be
helpful.
Le sam. 28 oct. 2023 à 22:14, Jarek Potiuk a écrit :
> Hey everyone,
>
> We had some discussions
+1
Le ven. 27 oct. 2023 à 19:16, Aritra Basu a
écrit :
> Sounds like a good time to set the process up. +1 from me as well.
>
> --
> Regards,
> Aritra Basu
>
> On Fri, Oct 27, 2023, 6:42 PM Vincent Beck wrote:
>
> > I like that. I also think it is important to have a process to remove
> >
I got the first "fully green pass" of the "Improve testing harness to
separate DB and non-DB tests" that looks stable and shows the "real"
numbers and improvements.
Copying it here as well from
https://github.com/apache/airflow/pull/35160#issuecomment-1784152557 as
this one will impact (I hope
