[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [che-dev] Release plans
|
Can we not make Che 6 master and 5.19 a side branch so if we need patches on 5.19 they’re done on that branch only and all other features go to master? SPI, IDE changes, etc... would all be PRs to master.
Ok I understand your points. But let's take current sprint for example. We have planned to introduce some new features that are independent from the SPI (CLI with OpenShift support, multi-tenancy on multi cluster, json logs etc...). I would like to keep SPI and these features separated. I would like to merge them to master as soon as they are implemented. It doesn't make really sense to wait for the SPI to merge them.
What I am proposing is to continue merging new features to master when it's about something that is not SPI related. And of course continue merging PRs on che6 branch when it is something that depends on the SPI.
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
--
Brad Micklea // Developer Products // 416.707.0792