I'm working on re-integrating older sets for the 6.06 release, and noticed "Permanent Fame" is being displayed as "Permanent F"
It would be handy if resizing of the field was possible.
I didn't merge this into RC2 and it doesn't appear that James did either, it has only been placed into 6.07.0. please comment to grab my attention, but closing and putting the wrong versions will confuse me and make the release notes incorrect. Technically the reviewer that merges this in should be marking the version too...
The last few closed issues are all set to the incorrect versions. Everything defaults to master which is the development branch, aka 6.07.x series currently. Until this is merged into 6.06.x it should not be marked as resolved for 6.06.00RC2.
And with James resignation, if it isn't a bug it defaults to a majority vote from Code Chimps to push in anything marked as a feature into the production branch, in accordance with our bylaws.
If you have the time please ask on the dev list to get a consensus from the code chimps. I'd like to get rc3 out this next week.
Cheers,
On Friday, January 22, 2016, 11:04 PM, JIRA (for Connor Petty ) <jira@pcgenorg.atlassian.net> wrote:
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140_______________________________________________
Pcgen-trackers mailing list
Pcgen-trackers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pcgen-trackers
My apologies, I was unaware that the JIRA issues were used for the release notes. I was making my best judgement as to what should be put into 6.06.x release, but you are correct, that should be up to a majority vote. I'll removing all inappropriate fix version from my resolved issues and wait for them to be included into the 6.06.x branch. I just hope we don't loose track of the ones that actually do included in the next release.
Cheers!