These are chat archives for chocolatey/ChocolateyGUI

14th
Feb 2017
Richard Simpson
@RichiCoder1
Feb 14 2017 16:56
Will have to review.
Manfred Wallner
@mwallner
Feb 14 2017 17:01
thanks for finding this @RichiCoder1 ! :-)
Richard Simpson
@RichiCoder1
Feb 14 2017 17:02
Just came across my feed! At brief glance, looks like an excellent document. Def gonna read in depth later.
Gary Ewan Park
@gep13
Feb 14 2017 21:47
@RichiCoder1 definitely going to have to read through that, good find!
Richard Simpson
@RichiCoder1
Feb 14 2017 21:48
Yup :)
Manfred Wallner
@mwallner
Feb 14 2017 21:50
umm hi @gep13 and @RichiCoder1 - I've had the honor being added to the circle of 'power users' ... I've been playing around with https://github.com/chocolatey/ChocolateyGUI/projects/1 a little - I've removed chocolatey/ChocolateyGUI#331 from tab 'review' and don't know how to get it back
Richard Simpson
@RichiCoder1
Feb 14 2017 21:51
Huh
I have no idea
Gary Ewan Park
@gep13
Feb 14 2017 21:51
woot! Well done, and welcome to the team! :+1:
Richard Simpson
@RichiCoder1
Feb 14 2017 21:51
And yah, congrats!!
Manfred Wallner
@mwallner
Feb 14 2017 21:52
^^
Richard Simpson
@RichiCoder1
Feb 14 2017 21:52
AHA
Upper right hand, Add Cards, search 331, and the drag into appropriate column
/cc @mwallner
I've been meaning to clean up that project for a while haha
Why in the world you can't set the project from the issue itself, I'll never know. Projects still feel half baked :\
Manfred Wallner
@mwallner
Feb 14 2017 21:55
:D thanks!
Richard Simpson
@RichiCoder1
Feb 14 2017 21:57
@gep13 That site came out at a good time too haha. Still don't have as much time as I'd like to devote to GUI, so been trying to focus on at least being a good maintainer and making contributions easy and move quickly through the pipeline.
Richard Simpson
@RichiCoder1
Feb 14 2017 22:13
Though it doesn't matter if said contributions don't get released haha. I retargeted 0.15 for March 3, 2017 if that's good with you @gep13 (and now @mwallner :D)
Gonna hold myself to that date too and drop any features that don't make the cut.
Big focus for me for the rest of this week is going to be polishing settings and nagging @ferventcoder to get that background service business wrapped ;)
Gary Ewan Park
@gep13
Feb 14 2017 22:14
yip, that is fine with me, although, not sure how much direct help I will be able to offer now. Wife is currently in hospital getting ready to give birth to our second child. I will be "around" but no guarantee for how long, and when :-D
Richard Simpson
@RichiCoder1
Feb 14 2017 22:15
Oh my!
Good luck man :D
Gary Ewan Park
@gep13
Feb 14 2017 22:16
cheers :-D
Manfred Wallner
@mwallner
Feb 14 2017 22:16
:+1:
Richard Simpson
@RichiCoder1
Feb 14 2017 22:17
I guess, while you have free time, see what it takes to tee up the release? That's still all magic too me xD
Gary Ewan Park
@gep13
Feb 14 2017 22:19
@RichiCoder1 this is where the lack of Cake.Recipe documentation is going to come back to bite me, I need to get that sorted out, but the process is exactly the same as we follow on the Cake project, so if you have any doubts, you can bug @devlead or @patriksvensson, and they should be able to keep you right. The basic flow goes like this though....
  • do all development work on the develop branch
  • assign all issues/pull requests that you want to include in the next release against the 0.15.0 milestone, and make sure that they are closed, and that they have exactly one label associated with them (and that label should be one of the ones that appears in the GitReleaseManager.yml file
  • once development is complete, create a release branch called release/0.15.0
  • update any documentation that needs to be published as part of this release
Rob Reynolds
@ferventcoder
Feb 14 2017 22:22
I will take a look into background service and why it isn't picking up tomorrow
Gary Ewan Park
@gep13
Feb 14 2017 22:22
  • run the command .\build.ps1 -target releasenotes (this will require a couple of environment variables to be set locally, so that this can execute, i.e. your GitHub token, if you look in the credentials.cake file in the Cake.Recipe folder in the tools folder, you will see the required environment varialbes for GitReleaseManager)
  • the above will generate a set of release notes on GitHub
  • merge the release branch into the master branch, and push
  • if that works, go to the GitHub Release, which will be in draft format, and click publish, which will trigger another build. if all works, this will publish a number of build artifacts, including the downloaded release notes, to appveyor
  • once those artifacts are published, you should be able to hand those off to @ferventcoder for signing with the choco certificate
Rob Reynolds
@ferventcoder
Feb 14 2017 22:24
my name all over this :D
Gary Ewan Park
@gep13
Feb 14 2017 22:24
  • once that is done, you should be able to push out the choco package, to chocolatey.org
Richard Simpson
@RichiCoder1
Feb 14 2017 22:25
@ferventcoder Sounds good. Just let me know if I can do anything to help, or if you get blocked.
@gep13 Sounds good! So dropping RTM package into Chocolatey will be a manual process? Sounds good.
Gary Ewan Park
@gep13
Feb 14 2017 22:25
does all of that make sense?
@RichiCoder1 for now, yes. Ultimately, I think we can automate it, but baby steps
Richard Simpson
@RichiCoder1
Feb 14 2017 22:25

Yup! Let me capture that in a MD for future reference. Might want your help with

  • assign all issues/pull requests that you want to include in the next release against the 0.15.0 milestone, and make sure that they are closed, and that they have exactly one label associated with them (and that label should be one of the ones that appears in the GitReleaseManager.yml file

and to verify w/ you necessary env variables for -target releasenotes

@gep13 Becuase we're manually signing, I actually prefer the manual step for now
Gary Ewan Park
@gep13
Feb 14 2017 22:26
agreed
blob
blob
those are the two that you will need
Richard Simpson
@RichiCoder1
Feb 14 2017 22:28
That's a lot of enviroment! Haha. But only the Github keys are need for release? Sounds good
Gary Ewan Park
@gep13
Feb 14 2017 22:28
if you haven't already got an access token generated, you might want to go ahead and do that
correct, all the other variables are already plugged into AppVeyor
Richard Simpson
@RichiCoder1
Feb 14 2017 22:28
Yup, already have on for other stuff.
Neat :3
So we just have to clean up the milestone issues and we should be good....
Gary Ewan Park
@gep13
Feb 14 2017 22:28
it is only the tasks that you need to run locally, i.e. generate release notes, where you need to pull in the local varialbes

So we just have to clean up the milestone issues and we should be good....

yes, I believe so

you will notice in the above, that I have actually turned off some of hte publishing steps for ChocolateyGUI, as we want to do them manually
instead, it will only published to AppVeyor
normally, all of these steps are on
Richard Simpson
@RichiCoder1
Feb 14 2017 22:30
Is our myget feed scooping up artifacts from AppVeyor then?
Gary Ewan Park
@gep13
Feb 14 2017 22:30
no, the same generated package is pushed to MyGet, and uplaoded to AppVeyor
two seperate actions, which can be controlled
Richard Simpson
@RichiCoder1
Feb 14 2017 22:31
Ah, ok.
Gary Ewan Park
@gep13
Feb 14 2017 22:31
i.e. AppVeyor will almost always work, but as we have seen, MyGet might fall over
Richard Simpson
@RichiCoder1
Feb 14 2017 22:31
Oh yah, what's the process if want to release a "RC"?
Gary Ewan Park
@gep13
Feb 14 2017 22:31
but MyGet is easier to consume than Myget
when you create the release branch, the generated build number will be 0.15.0-beta0001 or somethign similar to that
tag that release branch with that same version number, and grab the generated artifact from AppVeyor and push out
Richard Simpson
@RichiCoder1
Feb 14 2017 22:32
And then I can just place the AppVeyor artifact on Choco community feed
Cool :)
Gary Ewan Park
@gep13
Feb 14 2017 22:32
after tagging, the next version number will be 0.15.0-beta0002 etc
GitVersion FTW!
Richard Simpson
@RichiCoder1
Feb 14 2017 22:33
Yup! <3 GitVersion
Gary Ewan Park
@gep13
Feb 14 2017 22:33
ok, I need to hit the hay
Richard Simpson
@RichiCoder1
Feb 14 2017 22:33
Go to sleep man! Thanks for the help :)
Gary Ewan Park
@gep13
Feb 14 2017 22:33
i will let you mull over all of the above
and shoot me any questions that you might have
Richard Simpson
@RichiCoder1
Feb 14 2017 22:33
:+1:
Gary Ewan Park
@gep13
Feb 14 2017 22:33
will be on/off line for the next short while
but I will check in every so often
Richard Simpson
@RichiCoder1
Feb 14 2017 22:34
I don't imagine much interesting will happen into next week anyways. I'll keep you in the loop and let you know if I have any questions. Otherwise, get some rest and take care of your wife and kid(s) ;)
Gary Ewan Park
@gep13
Feb 14 2017 22:36
will do, thanks!
talk to you later