Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Wait ... don't release yet!

Hi David,

Thanks. Unreleasing is quite straightforward:
- Removing a composed children p2 repository (the target release)
- A minor change commit and push to hidden the downloadable zips.

Going for that, then.

On 22/02/2013 14:29, David M Williams wrote:
Individual projects should wait also. We are a "Simultaneous Release"
after all.

If you have already pushed your bits I don't think heroics are needed to
"undo", but I would at least wait to announce. There's often issues with
someone trying to update one thing, but another thing isn't released
yet, so p2 reports, errors, etc.

So, best to wait until we know what the plan is.

Apologies for the late notice,

From: Adolfo Sanchez-Barbudo Herrera <adolfosbh@xxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date: 02/22/2013 09:25 AM
Subject: Re: [cross-project-issues-dev] Wait ... don't release yet!
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

Hi David,

On 22/02/2013 14:14, David M Williams wrote:
 > All those plans would involve not releasing today.

Just wondering, if this "Wait ... don't release yet!" also implies
"individual" projects.

We (I) have already published our bits as planned (Only announce to the
forum is pending). Giving our non-dependency on EGit/JGit projects I
guess we may carry on with the plan, right ?

cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

Back to the top