Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Virgo/Community/Minutes-2010-07-20"

(New page: Category:Virgo Category:EclipseRT {{Virgo}} == Attendees == * Glyn Normington - VMware * Steve Powell - VMware == Discussion == 1. There has been quite a lot activity on Vir...)
 
m
 
Line 1: Line 1:
 
[[Category:Virgo]] [[Category:EclipseRT]]
 
[[Category:Virgo]] [[Category:EclipseRT]]
{{Virgo}}
 
 
 
== Attendees  ==
 
== Attendees  ==
  
Line 9: Line 7:
 
== Discussion  ==
 
== Discussion  ==
  
1. There has been quite a lot activity on Virgo CQs. Many have been approved but some need more work.
+
# There has been quite a lot activity on Virgo CQs. Many have been approved but some need more work.
 
+
# Contributions are starting to come in from the community, notable on the snaps prototype.
2. Contributions are starting to come in from the community, notable on the snaps prototype.
+
# I am writing up more detailed coding guidelines on the Virgo wiki for the benefit of contributors.
 
+
# There has been [http://dev.eclipse.org/mhonarc/lists/virgo-dev/msg00102.html discussion] of Maven build on virgo-dev. This is progressing but there seems to be a different philosophy for dependency management between components. In Maven, everyone normally gets to use the latest version of everything, within a certain version range. In Ant/Ivy with Virgo build, changes need to be promoted explicitly, which is more conservative.
3. I am writing up more detailed coding guidelines on the Virgo wiki for the benefit of contributors.
+
 
+
4. There has been [http://dev.eclipse.org/mhonarc/lists/virgo-dev/msg00102.html discussion] of Maven build on virgo-dev. This is progressing but there seems to be a different philosophy for dependency management between components. In Maven, everyone normally gets to use the latest version of everything, within a certain version range. In Ant/Ivy with Virgo build, changes need to be promoted explicitly, which is more conservative.
+

Latest revision as of 10:34, 10 August 2010

Attendees

  • Glyn Normington - VMware
  • Steve Powell - VMware

Discussion

  1. There has been quite a lot activity on Virgo CQs. Many have been approved but some need more work.
  2. Contributions are starting to come in from the community, notable on the snaps prototype.
  3. I am writing up more detailed coding guidelines on the Virgo wiki for the benefit of contributors.
  4. There has been discussion of Maven build on virgo-dev. This is progressing but there seems to be a different philosophy for dependency management between components. In Maven, everyone normally gets to use the latest version of everything, within a certain version range. In Ant/Ivy with Virgo build, changes need to be promoted explicitly, which is more conservative.

Back to the top