Skip to content
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

Merge the branches #52

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment
Open

Merge the branches #52

GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Given that it appears that poly is the main development trunk, the branches 
should probably be merged together into trunk.  If you think poly is stable 
enough, this could be set as a new release, and then a dev branch could be 
started from there.

As it is now, development might be a bit fractured with the multiple branches.  
Also, the current stable version is pretty old compared to what's already in 
poly.  (For example, the Overlay file is no longer required, etc.)

Besides, the code is small enough that stable releases could be made every few 
months.

Original issue reported on code.google.com by [email protected] on 8 Feb 2012 at 3:15

@GoogleCodeExporter
Copy link
Author

Not sure this is necessary.  If there is enough interest in making the polys 
branch the trunk (if enough people star this request), I will consider doing it 
when time permits.

Original comment by geocodezip on 8 Feb 2012 at 4:23

  • Added labels: Type-Other, Priority-Low
  • Removed labels: Type-Defect, Priority-Medium

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

No branches or pull requests

1 participant