I'm really sorry but I've been frustrated by hotel wifi all week. If anyone has the time to post the board report I'd appreciate it.
Thanks, Jeremy On 13 Oct 2015 14:20, "Christian Schneider" <[email protected]> wrote: > This is the versions view for Aries in jira: > > https://issues.apache.org/jira/browse/ARIES/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel > > For the projects to be released by bundle there should be versions on the > bundle level. For the projects to be released by subproject the versions > should be on the subproject level. > For subsystem I am not sure what applies. There was one vote mail but I > think there is no parent project. So I think it depends if individual > releases are planned. > > Example: > subsystem-2.0.4 <- marked as unreleased .. should be released on > 2015-10-07 if subproject level is applicable here > jpa-2.2.0 <- released on 2015-09-26 > jpa-2.3.0 <- unreleased > transaction-blueprint-2.0.0 <- released on 2015-09-25 > transaction-3.0.0 <- unreleased ... I plan to switch to releases per > subproject. So I created this already > > Christian > > On 13.10.2015 15:07, John Ross wrote: > >> I don't know exactly what "version management in jira" is referencing. >> Is there a link? >> >> On Tue, Oct 13, 2015 at 7:55 AM, Christian Schneider >> <[email protected]> wrote: >> >>> I typically create jira versions for the next release and the following >>> release of each bundle or subproject. >>> So people can set fix version to the upcoming release or to the next >>> release >>> to indicate it will not make it for the upcoming release. >>> >>> Then before the voting I make sure all issues of the version are resolved >>> and move issues accordingly. >>> After the vote I set the version to status released and set the release >>> date >>> to the date when the vote was closed. >>> >>> For old jira versions that were not released in jira but the released >>> artifacts were present I used the date of the artifact in maven central >>> as >>> release date. >>> >>> I hope everyone who does releases already has access to the version >>> management in jira. If not please speak up and I can take care of it. >>> >>> Christian >>> >>> >>> On 13.10.2015 13:47, John Ross wrote: >>> >>>> "I did put the JPA and Transaction releases in jira." >>>> >>>> I'm not quite sure what that means. Does it mean there was a ticket >>>> open that tracked the release? Does it mean you added the release >>>> version to the system so that it can be referenced by the "Fix >>>> Version/s" field? Both? Something else? >>>> >>>> On Tue, Oct 13, 2015 at 6:24 AM, Christian Schneider >>>> <[email protected]> wrote: >>>> >>>>> I did put the JPA and Transaction releases in jira. >>>>> I did not put the releases on the download server though .. Almost no >>>>> one >>>>> will download plain libs there. On the other hand the Apache release >>>>> policy >>>>> requires this. >>>>> >>>>> Christian >>>>> >>>>> >>>>> On 13.10.2015 13:04, Jeremy Hughes wrote: >>>>> >>>>>> True. Probably indicates we're not putting all our releases in jira. >>>>>> >>>>>> On Tue, 13 Oct 2015 12:02 David Bosschaert < >>>>>> [email protected]> >>>>>> wrote: >>>>>> >>>>>> -- >>>>> Christian Schneider >>>>> http://www.liquid-reality.de >>>>> >>>>> Open Source Architect >>>>> http://www.talend.com >>>>> >>>>> >>> -- >>> Christian Schneider >>> http://www.liquid-reality.de >>> >>> Open Source Architect >>> http://www.talend.com >>> >>> > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com > >
