-
Notifications
You must be signed in to change notification settings - Fork 21
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
Add github report to site generation. #9
Comments
Karl-Heinz, can you provide an example of what I've got to do? |
Okay, thanks! |
Looks to me like this is now working, but the current report is not showing lots of recently closed issues, presumably because they don't have an associated milestone. I don't appear to have rights to append the milestone to those closed issues. Also, are these changes worthy of moving to 1.1 rather than 1.0.2? Finally, can I call a vote on a release or is that something that only committers do? |
Hi, Ross,
why did you remove the information from changes.xml?
Thanks,
Jochen
…On Thu, Feb 1, 2018 at 5:56 AM, Ross Lamont ***@***.***> wrote:
Closed #9 <#9> via
3491ff1
<3491ff1>
.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABAaGem4UHz5emOLhQh3pu9gzJJELIkzks5tQUQAgaJpZM4G4sG_>
.
|
Hi Jochen, All that information is in the GitHub report (I only removed the 1.0.2 stuff which should be all recorded in GitHub). I checked around some other pre-github projects and it seems that people either use the changes report or the GitHub report, so I also turned off the changes report. Personally I think keeping the changes report in, but making a clean cutover to the GitHub report has some value, but I can see that would be confusing. Cheers |
Hi, Ross,
okay, I was just asking. Lets see, how this turns out. Might be, I return
to that later, because personally I am all in favour of having things in
one place. (We are working on the sources anyways, and that's where
changes.xml is located.)
Jochen
…On Thu, Feb 1, 2018 at 11:37 PM, Ross Lamont ***@***.***> wrote:
Hi Jochen,
All that information is in the GitHub report (I only removed the 1.0.2
stuff which should be all recorded in GitHub). I checked around some other
pre-github projects and it seems that people either use the changes report
or the GitHub report, so I also turned off the changes report.
Personally I think keeping the changes report in, but making a clean
cutover to the GitHub report has some value, but I can see that would be
confusing.
Cheers
Ross
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABAaGaS8GCdWMz6PyIlVDt8az2fichhXks5tQjy9gaJpZM4G4sG_>
.
|
No description provided.
The text was updated successfully, but these errors were encountered: