Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] Release plans

Perhaps, sharing a list of features that rh-che is planning soon with deadlines can help better understand priorities? Sergey has mentioned that 5.20 is possible for some relatively urgent must -have's.

Another good list would be what Che6 lacks compared to Che5 when it comes to running it on OpenShift and OSIO in particular. Only this way we can have some estimates.

On Fri, Oct 13, 2017 at 1:03 PM, Stevan LeMeur <slemeur@xxxxxxxxxx> wrote:
Thomas' questions are legitimate and I think we need to answer those in order to take a well-informed decision.

Today, we have no sense of the status of spi+multi-user/multi-tenant on OSIO. With a plan like the one proposed, we don't know if it's going to take few weeks or few months before we are able to deploy 6.x on OSIO. 

I agree that the introduction of the new SPI on master, should not break anything that is already running. 
If we are not able to run the new version of Che with the spi on OSIO with the same capabilities than the version we are deploying today - then it means that the SPI is not ready and should not be merged.

So I'd like to understand where we are, before moving forward and merging the SPI. 

For our teams, our main priority must be to get OSIO running the latest version of Che asap. That's critical to us. All the rest, around single/multi assemblies, is less important for now. 

I don't see why we would even do a release of che 6, if we know that we are not able to run it on OSIO.

@Sergii: since mario's team is rushing to get 5.19 multi-tenant on OSIO, can you lead that analyze?







On Fri, Oct 13, 2017 at 10:20 AM, Thomas Mäder <tmader@xxxxxxxxxx> wrote:
On 10/13/2017 01:24 AM, Brad Micklea wrote:
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.

Here come my 0.02CHF.

So we create a branch "5x-bugfix" off the 5.19.0 tag. No featurework is done in 5.x-bugfix. Then merge spi-branch into master. 5.x-bugfix becomes the branch we base our releases on until master is again stable enough to can spin releases off it.

I think we all agree that Che-6 is the new hotness and we all want to move to that as soon as feasible, right? I guess what the openshift-che team is worried about is this:

1. When is Che 6 good enough to be used on openshift.io?

2. Do we need to port features in rh-che from che-5 to che-6? How long is that going to take?

3. Is there stuff in che/master that is not in che/spi?

The main question is: when will we (openshift-che) be able to resume delivering value based on che-6? If the answer is: "December", we have a problem, if it is "next week", nobody cares.

/Thomas


_______________________________________________
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



--

STEVAN LEMEUR

PRODUCT MANAGER

Red Hat 

slemeur@xxxxxxxxxx    M: +336-87-11-27-55    


_______________________________________________
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




--

Eugene Ivantsov | Docs&Support |eivantsov@xxxxxxxxxxx



Back to the top