Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] capability bundles to be removed from Helios build aggregation


The paragraph say you must do one of two things (bundle or document).  Your choice as to which you do.  To do neither is not one of your choices.  


>  I myself would vote for removing that requirement altogether.

You probably meant this figuratively, such as is ".... if I was on the planning council, here is what I would do ... ", but in case there is confusion, we do not all vote on these items as one big group, and you should voice your opinions to your PMC and Planning Council representative.





From: Eike Stepper <stepper@xxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 02/12/2010 01:19 AM
Subject: Re: [cross-project-issues-dev] capability bundles to be        removed        from        Helios build aggregation
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx





Am 12.02.2010 07:11, schrieb David M Williams:

Can you recommend how this can be improved: "...
These may be provided in a separate plugins and features to facilitate inclusion
and reuse by consumers in product development, or simply well documented so adopters can reuse via copy/paste."

>From past releases I have the strong association "capabilities -> bundles -> must-do". And that paragraph appears in a section that starts with "The requirements in this section must be met...". I recently asked someone (Thomas Hallgren or Ed Merks) if I still *must* provide capabilities bundles. I was referred to this paragraph and the answer was "Yes!". An indication that there is potential for misunderstanding. I myself would vote for removing that requirement altogether.

Cheers
/Eike

----

http://thegordian.blogspot.com
http://twitter.com/eikestepper





From: Eike Stepper <stepper@xxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 02/12/2010 01:09 AM
Subject: Re: [cross-project-issues-dev] capability bundles to be removed        from        Helios build aggregation
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx






Am 12.02.2010 07:02, schrieb David M Williams:


Sure. It means you don't have to provide one,

Should
http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php be updated accordingly, then?

Cheers
/Eike

----

http://thegordian.blogspot.com
http://twitter.com/eikestepper


if you otherwise document what should go it it, to make it easier for products or EPP packages to "reuse" your recommended capabilities.

From: Eike Stepper <stepper@xxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 02/12/2010 12:49 AM
Subject: Re: [cross-project-issues-dev] capability bundles to be removed from        Helios build aggregation
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx







Ping. Somebody an opinion on capabilities bundles?

Cheers
/Eike

----

http://thegordian.blogspot.com
http://twitter.com/eikestepper


Am 06.02.2010 19:24, schrieb Eike Stepper:
Hi Dave,

Does this mean I also do not have to maintain capabilities bundles?

Cheers
/Eike


Am 12.01.2010 08:37, schrieb David M Williams:


I've opened a bug to track this task, in general.


https://bugs.eclipse.org/bugs/show_bug.cgi?id=299344

In short, projects need to build their own capabilities bundles, or provide adequate documentation for what a package or product builder needs to know.

The reason I'm posting here to cross-project is because I want to ask if there's any problem doing this by M5? I know there's not much time left,
but ... would like to get started unless it impacts some package or product maintainers too severely.

So, if it does impact too much, please comment in the bug, and I can make the change right after M5 is declared.

Much thanks,


_______________________________________________
cross-project-issues-dev mailing list

cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




_______________________________________________
cross-project-issues-dev mailing list

cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list

cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




_______________________________________________
cross-project-issues-dev mailing list

cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
 
_______________________________________________
cross-project-issues-dev mailing list

cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev




_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
 

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



Back to the top