You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: