GitHub user hansva added a comment to the discussion: 2.17 Roadmap and goals
I am still wondering what this multi-project structure looks like and how it is managed. Are we talking multiple projects in a mono-repo, or does each project have its own git repository? How do you then manage releases and the life cycle of a project? How and when is the decision made to turn something into a new project? And I totally disagree on the second part. We have to make things simple but I think we have come at the day and age that ETL processes are considered as code and core parts of an organisation. So they should follow the same best practices that we use for code. I've seen the "extended project home" thing go wrong way too many times in the past. Someone changes something on a shared pipeline, and you have 5 teams yelling the next day because their processes have gone down because of a change they didn't ask for and didn't know was going to impact them. GitHub link: https://github.com/apache/hop/discussions/5980#discussioncomment-14934605 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
