|
||||||||
|
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'm not against the idea of multiple stacks files, but, I don't think we should create a second file without being clear on a few things. By declaring that it'd "only be used by JBDS" seems to make its scope "JBDS responsibility" and removes your hands from keeping it up to date and accurate. If that's what we wanted, we would just maintain our own stacks.yaml and not even involve you. So we need a better 'scope' of the document than just 'only used by jbds'.
1) What is the scope of each document. This should not even mention consumers such as JBDS, but be more open to who's consuming it while being more exact on scope.
2) When do items become 'legacy', ie, when would they need to be moved from the primary stacks to the 'legacy' file?
Take for example, seam. Currently seam 2.3.0 is in this patch. If a 2.3.1 comes out, do we remove 2.3.0 from the primary stacks and move it to the 'legacy'?
There needs to be some rules here as to what we're planning on doing. Otherwise it'll turn into a big mess.