Re: [cross-project-issues-dev] Status and outlook for Indigo M7

[David M Williams <david_williams@xxxxxxxxxx>]

> On Sequoyah file, we have disabled the Pulsar repository, as we have
> previously talked about. 
> Sequoyah won't support this repository anymore, but since this train
> is running, we understood that disabling it was the safe way to do
> it. We are ok with definitely removing it too, if it doesn't impact
> the release. 
>
> Please give us your word on what is the best approach, David. :)

Ah, yes, I remember now. And yes, let's leave it (disabled) for M7, but then immediately after (before the rush for RC1) let's remove it. Feel free to do yourself, or open a bug in cross-project if you'd like my help.

And, thanks to Chokri Mraidha for reminding me that mdt-papyrus stays. (to be honest, I was confusing Papyrus and Pulsar ... they both start with 'P' ... which I admit to just to illustrate the state of my late-night mind :) and why I need everything spelled out for me, repeatedly.

Thanks everyone,




Daniel Pastore ---05/04/2011 07:55:41 AM---Hi David, On Sequoyah file, we have disabled the Pulsar repository, as we have

From: Daniel Pastore <kpqb38@xxxxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 05/04/2011 07:55 AM
Subject: Re: [cross-project-issues-dev] Status and outlook for Indigo M7
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Hi David,

On Sequoyah file, we have disabled the Pulsar repository, as we have previously talked about. 
Sequoyah won't support this repository anymore, but since this train is running, we understood that disabling it was the safe way to do it. We are ok with definitely removing it too, if it doesn't impact the release. 

Please give us your word on what is the best approach, David. :)

On Wed, May 4, 2011 at 00:14, David M Williams <david_williams@xxxxxxxxxx> wrote:

As far as I can tell, everything is "on track" for easily finishing the common repository on Wednesday, our M7 +3 day.

There are still disabled features or repositories in the following three contribution files:

gyrex.b3aggrcon
mdt-papyrus.b3aggrcon
tools-sequoyah.b3aggrcon

I know at least some of these intentionally wait until +3 day to re-enable, but thought I'd list them here, in case there is an over site.

And, if I've understood some recent notes, we can remove the mdt-papyrus file ... right? (That is, there won't be a Papyrus EPP Package, right?) [apologies if I've misunderstood].

Let's set 3 PM Eastern as the deadline to get contributions "in", so the repository can be created by approximately 6 PM so EPP packages can be created by first thing "Thursday morning".
What this means is if you can't make it by 3 PM, be sure to notify us here on this list, with expected outlook, etc., so we'll know (if) to wait. And, let us know, Markus, if you need/prefer some other deadlines for EPP packages (I'm working from memory ... which is often faulty :)

Be sure to remember to test our staging repo [1] to make sure everything looks OK. I don't know if there have been any major changes to features, such as features removed from M6 to M7. If feasible, we'll create the release repo as a composite with M6 and M7, but if there are "conflicts" due to feature removals or something, then we will fall back to M7 only. Be sure to let us know if anyone already knows of issues that would make M6 and M7 "incompatible".

Thanks,

[1] http://download.eclipse.org/releases/staging/



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

-- 
Thanks,

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