Is Hubflow being maintained?

[webmaven]

It seems maintenance stopped in November 2014, with no progress being made toward the 1.6.0 release since then. Is @stuartherbert still working on hubflow? is anyone else at @datasift?

[stuartherbert]

I am still working on hubflow. I'm no longer with DataSift.

Main thing holding up 1.6.0 is that it needs a credible test suite, and I haven't yet written one. The next Storyplayer release is due next week. After that, I can switch over to completing hubflow 1.6.0 if there's folks out there who need support branches.

[webmaven]

I don't need the new features in the 1.6.0 branch, but it would be nice if the bug fixes were backported and a 1.5.3 release made.

[j-walker23]

1.6.0 would be awesome as well!

[stuartherbert]

I'm free this weekend to work on getting 1.6.0 out the door :)

[webmaven]

Looking forward to it!

[bitwiseman]

@stuartherbert - What can I do to help finish up 1.6.0? You said you need a credible test suite?

[stuartherbert]

@bitwiseman - any sort of test suite would be a huge help - even a manual set of test scripts would be gratefully received. 1.6.0 and onwards will have refactoring as well as fixes - esp as I want to port this to Windows too - and the last thing I want is to break the tool accidentally.

The main constraint at the minute is time. I'm currently a freelance consultant, and so far I've been kept very busy. Unfortunately, Gitflow / Hubflow (currently - I am going to change this!) isn't something I do any consulting on, which has made it hard to free up time to get 1.6.0 out the door and push on with further improvements.

Advice most welcome :)

[j-walker23]

@stuartherbert I forked this a while ago with the intentions of adding things that i personally cared about. Please know i am in no way a shell scripter. This was the first bash project i have ever looked at.

I did do my best to finish 1.6 on that fork by merging all open features into develop and fix all errors i could find. Then i went on to do any personal additions i wanted.

Please feel free to take anything i did right.
https://github.com/j-walker23/gitflow

ps, i found it pretty easy to figure the flow out and make whatever changes i wanted to. So thank you for the good code base : )

[webmaven]

@j-walker23 👍

[stuartherbert]

@j-walker23 thanks. I'm taking a look this evening to see what you've done :)

[stuartherbert]

Just in case anyone is wondering ... work is progressing on the test suite for Hubflow, covering 1.5.2 as well as the upcoming 1.6.0 release. As soon as this is done, I'll feel much more confident about finally tagging 1.6.0 for release.

[webmaven]

What does the test coverage % look like right now?

[wweaver]

I assume 1.6.0 never happened? Or is this happening in a different fork now since you said you don't work at datasift any longer?

[webmaven]

@stuartherbert, what is the status of HubFlow?

[stuartherbert]

At the moment, progress on Hubflow 1.6.0 has stalled.

From the initial testing I've done, Hubflow 1.6.0 has introduced some annoying new bugs. I'm tempted to say that it'd probably be best to go back to the last tagged release and start again on working towards Hubflow 1.6.0.

The last tagged Hubflow 1.5.x release continues to work well for my customers, in the mean time.

[webmaven]

@stuartherbert, that's disappointing of course, but hope lives on. 😉

Is the test-suite (for 1.5.2 as well as 1.6.0) closer to completion than the 1.6.0 branch itself? What % of the code is covered?

[stuartherbert]

@webmaven I want to get back to it. Maybe I should start a crowdfund campaign of some kind? Or maybe there's a firm or two out there willing to sponsor some of the work?

I don't have code coverage metrics. Not even sure how you'd generate those for testing bash scripts. The test suite didn't get very far before it showed up the problems with the 1.6.0 branch.

My preferred way forward is to have a re-think on how support branches should work, before attempting any code changes. I'm not sure that 1.6.0 has a great model in the first place.