Planning next release

[ronnix]

Hi everyone,

Trying to get things in motion for a long overdue release!

I'd like feedback from the community on which issues or pull requests are most important for you. Can you mention them in the comments below? Please keep it at one issue per comment, so that other people can add a +1 if this issue is important to them too, and explain in a few words why it's important to you. This will help for prioritising efforts for the next release!

Also, if there any pull requests that could be quick wins (ready to merge with little or no work), feel free to mention them too, and hopefully we can include them too.

Thanks for your help!

[optimum-web]

https://github.com/ronnix/fabtools/issues/274 would be very nice to have.

[deronnax]

Just release, it would already be awesome. And then quickly add a maintainer and start merging pull requests before everybody switch to something else

[ronnix]

FYI I just transferred the repo from my personal GitHub account to a new "fabtools" organization.

[ssteinerx]

@ronnix Not sure where it is on your radar, but I've started a Python3 port (to be used with fabric3).

My fork/branch is here.

I'm successfully using fabtools with fabric3 and Python3.5 and just fixing up things as I come across them.

If you're interested, I'll send over a pull request -- it'd be great if we could get TOX up to speed with the Python 3.5 build (I don't use 3.4), and the different requirements. Only differences are fabric3 in place of fabric, addition of six library for python2/3 compatible code simplification.

[medecau]

@ronnix why a new org vs the fabric org?

[ronnix]

That sounds like a good idea. Who should we talk to for this to happen?

[ronnix]

By the way, @hobbestigrou recently volunteered to review and merge pull requests, and I'm very happy that he released 0.20.0 on PyPI, so I'd like to take the opportunity to thank him!

[deronnax]

Jeff Forcier, the creator of Fabric. But I doubt he is interested since he's busy reinventing his own fabtools, Patchwork https://github.com/fabric/patchwork

[medecau]

I understand the reason now.

patchwork development seems abandoned without any relevant update for the last three years.

[ronnix]

Hey @bitprophet, do you think fabtools could be adopted in the fabric organization on Github, or do you think it's better that it stays in a separate org?

[bitprophet]

For now I'd vote separate org; I'm still hoping to make patchwork (or invocations, https://github.com/pyinvoke/invocations, or some merging of the two) into a real, best-common-denominator, core-project-blessed repo as per fabric/fabric#461 - likely as part of, or just after, the release of Fabric 2 / Invoke 1.0 (which is looming, thanks new employer!)

At that time I'd take a closer look at what to cherry-pick from fabtools & the others out there.

[bitprophet]

I should note, though, that I'm assuming at least a few of the dozen or so projects listed in that ticket are still kicking. If it turns out that fabtools is kind of the only game in town these days, then it might be a stronger argument for inclusion in the main fabric org, pending patchwork & friends.

[tony]

@bitprophet I'd like to see that working with fabric2, if you could make a pypi package with it. it'd be nice to move that process along, I think I heard about you mentioning patchwork somewhere else. The fabric google group I believe.

honestly, the sooner fabric2 gets production ready the better. as for the patchwork/fabtools/etc i don't care what projects owns reproducible commands, but I don't wanna duplicate porting them over. debugging this devops stuff is time consuming.

[hobbestigrou]

A new release will coming soon.

[shazaum]

#358 I believe to help more people.

[hobbestigrou]

It's merged.