Hi Jeremy,
thanks for the report.
I just would like to mention that I will prepare a blueprint core 1.8.3 fix
release.
Regards
JB
On 10/11/2017 01:16 PM, Jeremy Hughes wrote:
I'll be putting together the board report and submitting later today.
Please reply with anything you'd particularly
I'll be putting together the board report and submitting later today.
Please reply with anything you'd particularly like mentioned.
Thank you,
Jeremy
Looks good to me, Christian.
David
On 15 October 2015 at 10:48, Christian Schneider
wrote:
> I have assembled a report from the information in this thread and put it on
> the staging wiki.
>
> http://aries.staging.apache.org/community/boardreports/september-2015.html
>
I have assembled a report from the information in this thread and put it
on the staging wiki.
http://aries.staging.apache.org/community/boardreports/september-2015.html
If everyone agrees with it I can send it to the board.
Christian
On 14.10.2015 18:52, Jeremy Hughes wrote:
I'm really
I updated the staged version. Can you use this to send the report?
Christian
On 15.10.2015 16:11, Jeremy Hughes wrote:
Hi Christian, thanks for putting this together. I've just seen that it
has to be me to submit (!!)
http://www.apache.org/foundation/board/reporting but that's probably
ok as
Hi Christian, thanks for putting this together. I've just seen that it
has to be me to submit (!!)
http://www.apache.org/foundation/board/reporting but that's probably
ok as I have found some wifi! Although I'm now late.
CMS isn't working for me - I'm getting 404 when I use the bookmarklet
for
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" wrote:
> This is the versions view for Aries in jira:
>
>
Awesome. Makes things much easier. Thx
On 12 Oct 2015 19:36, "Christian Schneider" wrote:
> Hi Jeremy,
>
> Dan just made me aware of the reporter tool:
> https://reporter.apache.org/
>
> This is what it has for Aries.
>
> Christian
> -
>
> Report from the Apache
Looks like the releases section is not accurate...
David
On 13 October 2015 at 11:57, Jeremy Hughes wrote:
> Awesome. Makes things much easier. Thx
> On 12 Oct 2015 19:36, "Christian Schneider" wrote:
>
>> Hi Jeremy,
>>
>> Dan just made me aware of
True. Probably indicates we're not putting all our releases in jira.
On Tue, 13 Oct 2015 12:02 David Bosschaert
wrote:
> Looks like the releases section is not accurate...
>
> David
>
> On 13 October 2015 at 11:57, Jeremy Hughes 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
"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
I suppose we should agree on a format so the information is
consistent. Some of the ways I can think of that could be used to
enter the subsystems release information include the following.
SUBSYSTEM-2.0.4
SUBSYSTEM-OBR-1.0.4
Apache Aries Subsystem 2.0.4
Apache Aries Subsystem OBR 2.0.4
The versions I used in JIRA were subsystem-2.0.4 and
subsystem-obr-1.0.4, so I suppose I should use those on
https://reporter.apache.org/addrelease.html?aries, especially if we're
hopeful of some future integration. I'm not sure if these represent
the preferred format, however.
On Tue, Oct 13,
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
wrote:
> I typically create jira versions for the next release and the following
> release of each bundle or subproject.
> So
I'm teachable if I neglected to do anything as part of the subsystems release.
On Tue, Oct 13, 2015 at 6:04 AM, Jeremy Hughes wrote:
> True. Probably indicates we're not putting all our releases in jira.
>
> On Tue, 13 Oct 2015 12:02 David Bosschaert
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
Hi Jeremy,
Dan just made me aware of the reporter tool:
https://reporter.apache.org/
This is what it has for Aries.
Christian
-
Report from the Apache Aries committee [Jeremy Hughes]
## Description:
OSGi Enterprise Programming Model
## Issues:
- TODO - list any issues that require
Some more releases:
Aries transaction blueprint 1.1.1
Aries JPA 2.2.0
Aries transaction blueprint 2.0.0
Aries blueprint-maven-plugin 1.2.0
List Activities
User list activity increased to about 30 msgs/month.
Dev list activity increased to about 300 msgs/month.
Development efforts
Main
Also, don't forget the initial release of Subsystem Gogo Command 1.0
handled by David.
On Sat, Oct 10, 2015 at 10:32 AM, Christian Schneider
wrote:
>
> Some more releases:
>
> Aries transaction blueprint 1.1.1
> Aries JPA 2.2.0
> Aries transaction blueprint 2.0.0
> Aries
Hi everyone, we're due to report to the board this month, so I'm
collecting information. Please email back with anything you'd like
included.
Thanks,
Jeremy
A few new releases as tracked in
https://issues.apache.org/jira/browse/ARIES-1377.
subsystem-bundle:2.0.4
subsystem-api:2.0.4
subsystem-core:2.0.4
subsystem-obr:1.0.4
On Sat, Oct 10, 2015 at 5:20 AM, Jeremy Hughes wrote:
> Hi everyone, we're due to report to the board this
22 matches
Mail list logo