Clarity on release process

[Ross Lamont]

Hi all,

Doing a release (http://www.mojohaus.org/development/performing-a-release.html) for the first time, I couldn't work out what to do here:

• Record the release date for the version in the plugin's GitHub project and create a new version for future development/issues.

I figure someone else might have this problem later.  Where do you record this, or is it even valid anymore?  GitHub automatically tags and dates the release.  Could this be only relevant for projects using the changes plugin, where there is a place for the release date? Or does this somehow relate to GitHub milestones?  I went with the later, but there was still nowhere to put the release date.

Cheers

Ross

[Anders Hammar]

That is probably an old sentence inherited from the Codehaus JIRA days, which just have been changed to say Github instead of JIRA. It could probably be rewritten/improved.

Wrt Github I think what we need to do is to close the milestone. It is also possible to state the "due date", although I think that adding a due date when the release has been date is too late. So this sentence should instead state to close the milestone and create new milestones for future dev/issues.

Can you take care of updating this?

/Anders

--
You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev+unsubscribe@googlegroups.com.
To post to this group, send email to mojoha...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mojohaus-dev/e3313a9f-8fd0-476f-81ea-b810baf5fd13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ross Lamont]

Will do.

On Saturday, February 10, 2018 at 1:38:46 AM UTC+11, Anders Hammar wrote:

That is probably an old sentence inherited from the Codehaus JIRA days, which just have been changed to say Github instead of JIRA. It could probably be rewritten/improved.

Wrt Github I think what we need to do is to close the milestone. It is also possible to state the "due date", although I think that adding a due date when the release has been date is too late. So this sentence should instead state to close the milestone and create new milestones for future dev/issues.

Can you take care of updating this?

/Anders

On Thu, Feb 8, 2018 at 3:54 AM, Ross Lamont <ross.la...@gmail.com> wrote:

Hi all,

Doing a release (http://www.mojohaus.org/development/performing-a-release.html) for the first time, I couldn't work out what to do here:

• Record the release date for the version in the plugin's GitHub project and create a new version for future development/issues.

I figure someone else might have this problem later.  Where do you record this, or is it even valid anymore?  GitHub automatically tags and dates the release.  Could this be only relevant for projects using the changes plugin, where there is a place for the release date? Or does this somehow relate to GitHub milestones?  I went with the later, but there was still nowhere to put the release date.

Cheers

Ross

--
You received this message because you are subscribed to the Google Groups "mojohaus-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to mojohaus-dev...@googlegroups.com.