Git-subrepo: Any news on 0.4.0 release?

[barrettc]

Is there a timeline on the 0.4.0 release being official? I've been using the release branch and it has solved some of the issues my team has encountered. I'm eager for it to become an official release and homebrew package updated - just curious on the timeline.

[grimmySwe]

@ingydotnet What do you say, any spare time in your busy schedule?

[ingydotnet]

@grimmySwe I spent some time on Saturday, and will spend some time each day this week. Will keep you up to date. Thanks!

[FanchTheSystem]

@ingydotnet So what's up with 0.4.0 release ?

[ingydotnet]

@FanchTheSystem I'm thinking that I should probably go ahead and make release/0.4.0 branch be master, and then fix the things I don't like later. But I should probably at least review to see what I'm setting myself up for...

[bohansen]

If one is starting with subrepos from scratch which version is recommended until 0.4.0 is out?

[grimmySwe]

@bohansen I might be biased but I would recommend the "release/0.4.0" branch, anything prior to that would most likely get you some issues.

We are using 0.4.0 in production and as far as I know there are no major issues.

[bohansen]

Thanks, I'll give 0.4.0-branch a spin. There was a few tests not passing when running "make test", but that's maybe expected currently? I like the thorough test setup :+1:

[grimmySwe]

@bohansen If you have failing tests, please make an issue and state the environment. As far as I know, all tests pass. But as there are plenty of different platforms out there you might have something special.

[FanchTheSystem]

We are using 0.4.0 branch in production too ;)

[ingydotnet]

Hi all,

Apologies for the MIA. I am preparing for a couple big conference talks next week. I plan have time to work on the subrepo release between June 10-16.

Feel free to bug me then!

[FanchTheSystem]

@ingydotnet: Hope your conference talks was a success :) Maybe now you have some time for the next subrepo release ;)

[ingydotnet]

@FanchTheSystem Thanks. They were a great success. I also have another conference next Sunday, but I'm giving one of the same talks. I find myself in a position with not quite as much time as I had hoped. Also because I promised to coordinate a pyyaml release this week. :\

That said, I am going to focus on at least getting the subrepo release process figured out. ie Figuring out what must happen to do a release. I'll try to start a planning ticket today.

Anyone who wants to join #gitcommands on irc.freenode.net to help out, is welcome.

[ingydotnet]

Greetings all,

A couple points of good news. First I am done with all my conference work for this month. Next one is in August in Glasgow. :)

Second, more importantly, I have 2 projects that I'm very actively working on that have a big need for git-subrepo. I plan to be using subrepo a lot this week and will be using that as an excuse to dive in and get this long overdue release done.

I'll say it again... I don't know how many people here use IRC, but I'm always on IRC and it's the best way to get me to work on something specific. So as in my last comment: "Anyone who wants to join #gitcommands on irc.freenode.net to help out, is welcome." (Even if "helping out" is just nudging me along...)

[ingydotnet]

Hi guys,

I'm fire-fighting putting out the next PyYAML release, which is critical because it currently doesn't work with latest Python version.

But I'm still keen on this release. Hopefully I'll start by the end of this week or the start of next week.

Thanks for your patience.

[tobse80]

Hi all,

Are there any updates on releasing 0.4.0? The branch seems to work pretty well, but it's still not on master...

Thanks!

[ingydotnet]

Apologies for the delays. Hoping to review it this week. I know, I know...

[talios]

Any updates on the 0.4.0 release?

[ingydotnet]

@talios My life is finally calming down just a bit. I'm going to try to take a look at things this week.

I would like to just mush the release branch to master and fix anything I don't like later. I'd just like to know if I'm painting myself into any corners that I can't get out of later.

[tobse80]

Hi there,

any news on releasing 0.4.0 as master?

My experiences so far: release/0.4.0 solves issues for the standard subrepo clone/push/pull workflow, making it smoother and less error-prone. So why not moving forward?

Cheers!

[ingydotnet]

Hoping to look at it this week.

[juddgaddie]

How did it go ? ;)

[kohlhase]

We are still waiting for a release on master, any release, ...

[grimmySwe]

@juddgaddie I'll be happy to look at problems that arise, although I feel
that the project owner needs to give a go on actually performing a release.

Den tis 9 okt. 2018 kl 20:31 skrev Judd Gaddie [e-mail]:

@grimmySwe https://github.com/grimmySwe since you are supporting 0.4.0
for your own purposes are you perhaps interested in maintaing a release of
it?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ingydotnet/git-subrepo/issues/343#issuecomment-428300914,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGLigovg_wV8H5P-tyv3w7KgdHlzBAD8ks5ujOtkgaJpZM4R7k-K
.

[ingydotnet]

@grimmySwe I'll be in your timezone from for a few weeks starting next week. I'll contact you about figuring out a release plan.

[grimmySwe]

@Ingy dot Net [e-mail] That sounds good, I'll be in Essen most of
next week visiting the Spiel board game fair so that will be hectic.

Den ons 17 okt. 2018 kl 07:14 skrev Ingy döt Net [e-mail]:

@grimmySwe https://github.com/grimmySwe I'll be in your timezone from
for a few weeks starting next week. I'll contact you about figuring out a
release plan.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ingydotnet/git-subrepo/issues/343#issuecomment-430492087,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGLigtW5mWaPsB7To5lvObK-6IRYJ6VIks5ulryhgaJpZM4R7k-K
.

[ingydotnet]

Done and Done!

I had a brief call with @grimmySwe today and we agreed that making the 0.4.0
branch be master as-is was the best approach at this time. Any problems that
arise can surely be fixed.

Apologies to all for dragging this on for so long. Thanks to all for your
patience!

I have created https://github.com/ingydotnet/git-subrepo/projects/2 to plan the
next 0.4.1 release.