Skip to content

Update README for L5 release #19

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 11, 2015
Merged

Conversation

verkaufer
Copy link
Contributor

Just needs a release tag for release.

Just needs a release tag for release.
@toin0u
Copy link
Member

toin0u commented Mar 9, 2015

@verkaufer Thanks!

@toin0u
Copy link
Member

toin0u commented Mar 9, 2015

Maybe it can be a good idea to write something for Laravel 4 users don't you think ?

@verkaufer
Copy link
Contributor Author

You could make a new branch for the L5 release (maybe 0.5.x). That way the package remains compatible with Laravel 4 (in the 0.4.x branch) and retains its L4 documentation while also adding L5 support via the 0.5.x branch (with the L5 documentation above).

@toin0u
Copy link
Member

toin0u commented Mar 10, 2015

What do you think about making a branch for the actual version and use the master for the L5 ? We gonna release Geocoder 3.0 and I think it will be a good moment to release GeocoderLaravel 1.0

@verkaufer
Copy link
Contributor Author

That sounds perfect. So GeocoderLaravel 1.0 would be for L5 and 0.4.x would be for L4?

@toin0u
Copy link
Member

toin0u commented Mar 11, 2015

@verkaufer exactly :) but before to release 1.0.0 I'll tag the master branch 0.5 :)

@verkaufer
Copy link
Contributor Author

Sounds good! Just merge in this readme update when you do that :)

toin0u added a commit that referenced this pull request Mar 11, 2015
Update README for L5 release
@toin0u toin0u merged commit 3d1b547 into geocoder-php:master Mar 11, 2015
@toin0u
Copy link
Member

toin0u commented Mar 11, 2015

Thanks for all your comments - It helped a lot 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants