Let's just go with the current release plan for NatTable and consider it a 
learning  experience.

I'm not to concerned about a short time gap this once. 

Wayne

<div>-------- Original message --------</div><div>From: Dirk Fauth 
<[email protected]> </div><div>Date:2016-05-17  02:30  (GMT-05:00) 
</div><div>To: Wim Jongman <[email protected]>, Wayne Beaton 
<[email protected]> </div><div>Cc: Nebula Dev <[email protected]> 
</div><div>Subject: Re: [nebula-dev] Nebula release and graduation </div><div>
</div>@Wayne
Should I reschedule the NatTable release for a date after the Nebula release 
then?

@Wim
When do you plan to do the release? I planned end of May to be before Neon RC3. 
But if the review for nebula starts 1st of June that doesn't work out.

Am 15.05.2016 21:46 schrieb "Wim Jongman" <[email protected]>:
Excellent.thanks for the info.

 June 1 sounds great.

Cheers,

Wim

On Sun, May 15, 2016 at 6:13 PM, Wayne Beaton <[email protected]> wrote:
I'd rather just push hard on getting Nebula released.

At a minimum, can we just identify the components that are already being marked 
as "1.0" and include them in the release?

The IP Log looks pretty clean to me. I can add this to the June 1st review 
slot. All I need is review documentation and approval from the PMC.

As I said earlier, you can release any subset of the project code. The biggest 
challenge here, I think, is to create downloads that include only the stuff 
included in the release. So let me turn this around... can you create that 
download in time for a June 1st release?

HTH,

Wayne



On 14/05/16 12:43 PM, Dirk Fauth wrote:
@wayne

Do you mean I have to remove the RichTextEditor dependency for the NatTable 
release? That would be a big issue for other projects like papyrus!

Do you think it would be possible to do a graduation for nebula before the 
release train?

Am 14.05.2016 6:31 PM schrieb "Dirk Fauth" <[email protected]>:
Do we really need to do this? I mean we only publish the released widgets in 
the release repo. And for the incubation widgets we would have another repo. Or 
is that separation not enough?

Am 14.05.2016 4:24 PM schrieb "Wim Jongman" <[email protected]>:
Hi,


Wayne we must split the project in two because we cannot release all widgets. 
How do we achieve this?

Cheers,

Wim


On Fri, May 13, 2016 at 5:12 AM, Wayne Beaton <[email protected]> wrote:
This is what is in the Neon simultaneous release repository.

I'm a little concerned that these have been appearing in simultaneous releases 
for a while, Sure the world hasn't stopped turning, but this is a violation of 
the process.

Strictly speaking, NatTable should not be consuming the unreleased components 
from Nebula.
wbeaton@build:~> find downloads/releases/ -name *eclipse.nebula* | grep -v 
nattable
downloads/releases/galileo/200909241140/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar.pack.gz
downloads/releases/galileo/200909241140/aggregate/plugins/org.eclipse.nebula.widgets.compositetable.source_1.0.0.jar.pack.gz
downloads/releases/galileo/201002260900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar.pack.gz
downloads/releases/galileo/201002260900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable.source_1.0.0.jar.pack.gz
downloads/releases/neon/201512181000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201511041902.jar
downloads/releases/neon/201605061000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201604151927.jar
downloads/releases/neon/201605061000/plugins/org.eclipse.nebula.widgets.richtext_1.0.0.201604151927.jar
downloads/releases/neon/201603301000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201602191853.jar
downloads/releases/neon/201602051000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201602011643.jar
downloads/releases/kepler/201306260900/plugins/org.eclipse.nebula.widgets.compositetable.source_1.0.0.jar
downloads/releases/kepler/201306260900/plugins/org.eclipse.nebula.widgets.grid_1.0.0.HEAD.jar
downloads/releases/kepler/201306260900/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar
downloads/releases/mars/201510021000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201509022342.jar
downloads/releases/mars/201602261000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201602111357.jar
downloads/releases/helios/201102250900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar.pack.gz
downloads/releases/helios/201102250900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar
downloads/releases/helios/201009240900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar.pack.gz
downloads/releases/helios/201009240900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar
downloads/releases/helios/201006230900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar.pack.gz
downloads/releases/helios/201006230900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar
downloads/releases/indigo/201106220900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar.pack.gz
downloads/releases/indigo/201106220900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar
downloads/releases/indigo/201109230900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar.pack.gz
downloads/releases/indigo/201109230900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar
downloads/releases/indigo/201202240900/aggregate/plugins/org.eclipse.nebula.widgets.compositetable_1.0.0.jar

Clearly projects want to consume Nebula components and a few have been sneaked 
in. 

Regardless, however, Nebula has been around                           for a 
very long time and has never done a release. It needs to graduate.

Wayne


On 12/05/16 04:49 PM, Wim Jongman wrote:
Hey S. Gonzales!

This is only what NatTable consumes. What about the rest of the projects?

Wim

On Thu, May 12, 2016 at 10:46 PM, Wayne Beaton <[email protected]> wrote:
wbeaton@build:~> find downloads/releases/neon/ -name *eclipse.nebula* | grep -v 
nattable
downloads/releases/neon/201512181000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201511041902.jar
downloads/releases/neon/201605061000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201604151927.jar
downloads/releases/neon/201605061000/plugins/org.eclipse.nebula.widgets.richtext_1.0.0.201604151927.jar
downloads/releases/neon/201603301000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201602191853.jar
downloads/releases/neon/201602051000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201602011643.jar

HTH,

Wayne


On 12/05/16 04:44 PM, Wim Jongman wrote:
We should be able to investigate what is being consumed by the release train. 
If this also includes one or more of the "unsupported widgets" then we need to 
decide if we add those as well or let these consumers know that they are in 
violation.

David could you produce a list with references to org.eclipse.nebula projects?



On Thu, May 12, 2016 at 10:16 PM, Dirk Fauth <[email protected]> wrote:
As far as I understood Wim, the idea is to first clean up the list of 
committers, specify the widgets/projects that should be in the release and 
possibly update the widget versions to 1.0.0 to match the version rules 
regarding maturity.

From my point of view the set of widgets for the release is set. At least that 
would be what the community expects. What is currently communicated as released 
should be released. I think that would be the easiest way to proceed. Not sure 
if Wim planned to also move some of the incubation widgets to the release 
aswell.

Regarding the IP log, do we need to wait for the cleanup or should we send it 
in immediately via 
https://projects.eclipse.org/projects/technology.nebula/iplog/preview ?



On Thu, May 12, 2016 at 9:49 PM, Wayne Beaton <[email protected]> wrote:
A bunch of projects are already using Nebula widgets. This is a bit problematic 
from an EDP POV because Nebula has never done (AFAICT) a formal release and is 
still incubating.

It's long past time to do a proper release and graduate the project.

Can we do this soon?

AFAICT, the project downloads are IP clean, so getting the IP Log approved 
should only take a couple of seconds of effort.

The project is hosting downloads [1] (though, I'd prefer that you not use the 
term "Projects" like you are; that term is already confusing enough).

There is still lots of activity on the project, but it does seem that many/most 
of the widgets are stable.

What's stopping us from doing this?

Wayne

[1] https://www.eclipse.org/nebula/downloads.php

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
 

_______________________________________________
nebula-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev


_______________________________________________
nebula-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev


--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
 


-- 
Wayne Beaton
@waynebeaton
The Eclipse Foundation
 


_______________________________________________
nebula-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

-- 
Wayne Beaton
@waynebeaton
The Eclipse Foundation
 

_______________________________________________
nebula-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

_______________________________________________
nebula-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/nebula-dev

Reply via email to