Hey

It seems like you have made some good progress on this so I was wondering when you were going ot have a release candidate. I have a live site I would like to deploy it on but if you are heavily changing it I would rather not. I couldn't find anything on your main page about that so I opened a ticket (hope that's ok)

Cheers

Comments

GDrupal’s picture

@ShaneOnABike there is not plan to change any back-end logic.. but the UI perhaps will be very different. Although that change it's still on hold for now, waiting for the module's main sponsor to give it green light.

mgifford’s picture

Would be great to see this. I don't think it makes sense to wait for the modules sponsor at this stage given it's over a year now.

GDrupal’s picture

@mgifford you are right, I would like to first include some of the pending patches that I need to review and then we can talk about a release candidate for sure.

mgifford’s picture

That's great. Looking forward to seeing the release.

achton’s picture

Issue summary: View changes

Also really looking forward to an RC here.

The module is used by so many sites, it seems strange to not have a tagged release.

shaneonabike’s picture

Thanks for considering this and I totally agree that with a stable release it's easier to make patches tooo!!

joseph.olstad’s picture

Version: 7.x-1.x-dev » 7.x-4.x-dev

The 1x branch needs some tlc , more likely to put an rc for the 4x branch soon.

joseph.olstad’s picture

Assigned: Unassigned » joel_osc

Hi @joel_osc , looks like I don't have enough access to create a release, but I did tag an alpha version. Its probably about time that there is at least an alpha release.

Can you please try?

Stevel’s picture

The only 'tag' in the repository is the commit http://cgit.drupalcode.org/webform_localization/commit/?h=7.x-4.x&id=10b... . Should this not be a 'real' tag?

joseph.olstad’s picture

Hi @Stevel, while I have commit access, I was able to tag a commit, but I lack the rights to make it generate a release on Drupal.org , right now only GDrupal has access to do this. I've asked for this privilege , I'd actually like to make more co-maintainers and give out commit access to reliable developers like rv0 that has been contributing regularly (and possibly you as well) but right now it's myself, joel_osc , and GDrupal that have commit access and only GDrupal can make a release happen on drupal.org for now.

I saw your last patch on another issue, I'll try to commit that asap.

joseph.olstad’s picture

Status: Active » Fixed

we just tagged a 7.x-4.0-alpha2 release
it's now on drupal.org/project/webform_localization

Stevel’s picture

Thanks @joseph.olstad! I can see the 7.x-4.0-alpha12 release now. You might want to take a look at the git tree. The latest commit is not in the 4.x-branch, but it is in the latest alpha:

http://cgit.drupalcode.org/webform_localization/log/?h=7.x-4.0-alpha12

joseph.olstad’s picture

ok, Hi Stevel, I was looking into that but didn't have time to set it back to 4.x-branch , if you could please be so kind as to write the one or two git commands necessary I'll point the latest commit back to the 4.x-dev branch. spent quite a bit of time on this module lately but now I've got to get some other stuff done.

Stevel’s picture

Not 100% sure, but I think something like this should do the trick:

git checkout 7.x-4.x
git merge 7.x-4.0-alpha12
git push 7.x-4.x
joseph.olstad’s picture

git checkout 7.x-4.x
Already on '7.x-4.x'

git merge 7.x-4.0-alpha12
fatal: 7.x-4.0-alpha12 - not something we can merge

git push 7.x-4.x
fatal: You are pushing to remote '7.x-4.x', which is not the upstream of
your current branch '7.x-4.x', without telling me what to push
to update which remote branch.

joseph.olstad’s picture

Thanks @stevel
I re-cloned and then ran that command, then I got a warning about a merge conflict. Once I got that I was able to fix the conflict and push it up.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.