Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

[12:59:54 CDT(-0500)] <apetro> checking in
[13:06:03 CDT(-0500)] <apetro> How are things, battags?
[13:08:11 CDT(-0500)] <battags> hey
[13:08:19 CDT(-0500)] <battags> how's it going?
[13:08:34 CDT(-0500)] <apetro> eh. Lost a couple days to some kind of fever, but I'm managing.
[13:08:38 CDT(-0500)] <battags> I'm trying to figure out why 3.4.10 got tagged, but the artifacts never made it to the public repo
[13:08:43 CDT(-0500)] <battags> fever in the summer?
[13:08:54 CDT(-0500)] <battags> that sucks
[13:08:55 CDT(-0500)] <apetro> yeah. Not sure what that was. Something going around.
[13:13:37 CDT(-0500)] <apetro> alright. So, mechanical issues with the 3.4.10 tag-and-release
[13:13:43 CDT(-0500)] <apetro> anything else exciting to discuss?
[13:16:31 CDT(-0500)] <battags> I figured out what it was
[13:16:40 CDT(-0500)] <battags> apparently I typed release:prepare and forgot to do release:perform
[13:16:45 CDT(-0500)] <battags> but did the assembly step
[13:17:00 CDT(-0500)] <battags> apparently I need to make the release process have check boxes (wink)
[13:19:33 CDT(-0500)] <apetro> hmm.
[13:20:03 CDT(-0500)] <apetro> might actually be worth forking a Confluence page for each release and stepping through the release checklist there. Would that afford better opportunities for collab / multiple hands on things like the release announcement on website?

  • No labels