|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I honestly believe it's best to have one stacks file and simply add labels that consumers can filter on. If the stacks website wants to filter only on 'current' runtimes, then they should add their own label as to what's 'current' and filter based on that.
I'm not against separate files, but I think that becomes dangerous and leads to confusion in future maintenance. When things slip off from 'current' to 'legacy', we'll end up moving significant portions of files, or even duplicating them. I'm no stacks expert, but it seems less than ideal.