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

Clean up the repo #38

Open
nathanrice opened this issue Aug 7, 2018 · 1 comment
Open

Clean up the repo #38

nathanrice opened this issue Aug 7, 2018 · 1 comment
Labels

Comments

@nathanrice
Copy link
Contributor

Tag Releases

I'm not terribly concerned about having the pre-1.0 releases tagged, but we should definitely tag all new releases moving forward.

Assign closed issues to milestones

Any issues that were fixed in the 1.0.0 release should be assigned to the 1.0.0 milestone. Moving forward, we'll know what version we're working on for a release, and do this beforehand.

The 1.0.0 milestone can then be closed.

Repo standardization

@nickcernis @marksabbath It's worth having a conversation (at some point) about standardizing repos with your grunt tools, issue labels, etc.

@marksabbath
Copy link
Contributor

Totally agree with you @nathanrice !

Every line of Gruntfile.js is being written thinking about that. The main target would be having a minimum set of tasks that must be run to help standardize the repository and dev. flow, help to test and assure some basic tasks and also reduce time either in development or releasing the plugin.

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

No branches or pull requests

2 participants