Falcon rev control is crazy

6 replies [Last post]
Joined: 04/09/2012
Points: 193

Users here have been told to use the Falcon branch for our general use.

Recent experience (between mid Dec and yesterday it wouldn't build for us) and a quick look at the Falcon change logs show this may not be a good idea. But... there is no alternative.

The Falcon branch of KalturaServer has had 23 commits in the last two days. Twenty Three!!!

This seems more like a nightly build branch than a user trial branch.

Would it be possible to get a slightly more stable branch for us to use? It would really help especially since we don't have a good way to make minor/daily updates to our working instance.

Developer thoughts are appreciated on this topic please.

Joe

Joined: 01/05/2009
Points: 1697

https://github.com/kaltura/KalturaServer/commits/falcon is the latest release of the Falcon version.
This is indeed the latest stable version, updates made to it are only bug fixes. No new features or additions.
I can't see why you would like a frozen release without the latest bug fixes..

Joined: 04/09/2012
Points: 193

It just seems to me like 23 changes in two days is a lot of changes for a user trial and for three weeks one of those changes prevented new builds from compiling. It would be interesting to see how many per week but there are visually a lot of blue dots on that 'Falcon' branch.

Latest bug fixes are good but a simple regression test that includes a new install and basic upload prior to releasing to user trials would be nice.

I can't see how anyone in the development community ever ran any regression tests after the many many commits.

I suppose it is a bit of a moot point but it was really frustrating spending days (along with at least two or three others here) getting builds to try to compile and diagnosing that a change somewhere in mid-Dec was breaking things.

That bad commit was just this week corrected but that really isn't the point either.

There has to be some balance between 'latest' and 'stable'.

Joined: 01/05/2009
Points: 1697

Agreed. Definitely, a separation between "last-known-stable", "latest" and "next-version" is needed.
Since we just made the move to github, it will take little while till the process is finalized. As the new git based install gets more stable, we'll find the balance between these version tags. Currently 6.0 is still in "public beta" mode, which is to say, it's stable, but not enough to be frozen from fixes.
We'll probably be able to decide on a stable package during early February, as all serious bugs are discovered and fixed.

In addition, as part of Gemini (next release) an automated testing mechanism is planned. You can see it at:
https://github.com/kaltura/KalturaServer/tree/master/tests
Achieving a faster detection of post-install problems, and potentially allow to run a public CI system on the github based install.

Joined: 05/13/2009
Points: 164

I'm sorry for the current state of the falcon branch, I hope to have it fixed by the end of the day, and I'll freeze a working copy with a tag like v6.0.0 once we've gotten to a working version.

As always, thanks for trying out our new toolchain, and keep on sending in the feedback, it is very valuable to us.

Joined: 03/08/2012
Points: 22

Thanks for freezing a copy of the packager, it's made testing and installing much simpler. You've mentioned above that a stable package might be decided upon in early February. There haven't been any major changes to the ce-packager or KalturaServer repos for nearly a month now (that I can tell - just some minor changes to docs). Do you folks anticipate that this will be the first stable version or are there any big changes that might be pushed over in the next couple of weeks?

Joined: 11/02/2010
Points: 4

So can anybody give me a description beween the different branches?
I find it hard to understand what version should I use and what is the latest / next version / current stable git repos.