On 27 Apr 2012, at 14:04, Wayne Beaton wrote:
Isn't this what Virgo *is* doing?
Yes, kind of. The main issue is that the full release process feels like overkill when we want to release samples, so in practice, we tend to release the samples at the same time as the runtime to minimise the overheads.
The EDP supports the ability to include some subset of the project
code in a release. So, releasing de facto components separately is
acceptable. My only concern is community confusion, which is
probably not a big issue in this case.
The IP logs are more of a technical issue. The current
infrastructure works on a project-basis. I can update the scripts to
run against some subset of the repositories and some subset of the
bugzilla records (assuming you can form a coherent query for the
records that affect a particular release). Automating the extraction
of information from CQs is a little harder and will require baking
some means of categorizing CQs into IPZilla.
But it all sounds doable.
In the meantime, IP Logs will have to be manually managed. Perhaps
it might be time to resurrect the work that I was doing on Woolsey;
it was designed specifically to help with the process of manually
updating/managing IP Logs. I haven't looked at it in a while, so
this may be less viable than I hope...
Wayne
On 04/27/2012 08:47 AM, Glyn Normington wrote:
On 27 Apr 2012, at 13:36, Campo, Christian wrote:
I agree that releases should not be tied to ACL
group.
So in other words if we had a single Gemini project,
I think you should still be able to release Gemini Web
and Gemini Blueprint as independent releases from this
one project.
Virgo has a similar requirement. We'd like to be able to release
the runtime, the tooling, and the samples independently of each
other.
Not so sure about IP Logs. I think it probably really
hard to manage multiple IP Logs for one project. Still
couldnt you submit the whole IP Log once you try to
release any of the components ?
That would be a little messy as it would be necessary to
trim down the IP log to the parts required. This would
potentially require a concentrated piece of work at release
time, whereas the IP log today can be maintained incrementally
and just tidied up at release time, which is more manageable.
christian
I agree with thomas on that as well
jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx
On Fri, Apr 27, 2012 at 07:19, Thomas Watson <tjwatson@xxxxxxxxxx> wrote:
In my opinion we should be able to have
releases that are not directly tied to ACL
groups. I fail to see why the two must be
directly related. But perhaps I am missing
something.
Tom.
<graycol.gif> Glyn
Normington ---04/27/2012 05:21:53 AM---At
the last RT PMC call there was discussion of
Gemini's subproject structure. Recently, one
of the subprojects temporarily had
<ecblank.gif>
|
<ecblank.gif>
Glyn Normington <gnormington@xxxxxxxxxx>
|
<ecblank.gif>
|
<ecblank.gif>
Runtime Project PMC mailing list <rt-pmc@xxxxxxxxxxx>,
|
<ecblank.gif>
|
<ecblank.gif>
04/27/2012 05:21 AM |
<ecblank.gif>
|
<ecblank.gif>
[rt-pmc] Gemini Subprojects |
At the last RT PMC call there was
discussion of Gemini's subproject
structure. Recently, one of the
subprojects temporarily had no committers
and the thought was expressed on the call
that this could perhaps be avoided in
future by amalgamating the Gemini
subproject committers into a single ACL.
Presumably this would require amalgamating
the subprojects into one.
I spoke to Mike Keith about this and it
seems that it is necessary to keep the
subproject structure so that individual
subprojects can be released independently
of each other (which is essential). For
example, the subproject structure enables
IP logs to be managed and approved
separately.
So is the conclusion that we can't
amalgamate the ACLs without losing the
ability to release subprojects
independently of each other?
Regards,
Glyn
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc
-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: www.compeople.de
Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
USt-IdNr. DE207665352
-------------------------------------------------------------
<graycol.gif><ecblank.gif>_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse
Projects
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc
|
