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.

Sign up for GitHub

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

Jump to bottom

Convention on platform package naming (FAQ) #166

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

Convention on platform package naming (FAQ) #166

GoogleCodeExporter opened this issue Mar 24, 2015 · 1 comment
Labels
auto-migrated Milestone-1.0-beta.32 Priority-Medium Product-Core Type-Feature

Comments

@GoogleCodeExporter
Copy link 

Sean DeNigris is satisifed with the naming convention he describes in this 
post[1]. Probably worth documenting this as FAQ ...

[1] 
http://forum.world.st/Convention-on-platform-e-g-Pharo1-3-vs-Pharo1-4-package-na
ming-tp4167422p4170616.html

Original issue reported on code.google.com by [email protected] on 3 Jan 2012 at 7:45
@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 18 Jan 2012 at 7:06

  • Added labels: Milestone-1.0-beta.32
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Milestone-1.0-beta.32 Priority-Medium Product-Core Type-Feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter