[eclipse.org-architecture-council] Release process (or implementation of

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[eclipse.org-architecture-council] Release process (or implementation of release process) related bugs

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Thu, 28 Jun 2018 17:57:32 +0200
Delivered-to: eclipse.org-architecture-council@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipse.org-architecture-council>
List-help: <mailto:eclipse.org-architecture-council-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council>, <mailto:eclipse.org-architecture-council-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipse.org-architecture-council>, <mailto:eclipse.org-architecture-council-request@eclipse.org?subject=unsubscribe>

Hi all,

I've added 2 bugs following some of the points we discussed in our (very interesting and progress-making) call today:

* Bug 536428 - Consider continuous validation of IP Logs to speed up releases

* Bug 536429 - Centralize the full (as much as possible) tracking of release process on 1 single page (like a bugzilla issue)

They're mark as linked from

* Bug 496321 - [EDP] Lighten the burden for frequent releases

Cheers,
--

Mickael Istria

Eclipse IDE developer, for Red Hat Developers

Prev by Date: Re: [eclipse.org-architecture-council] Regrets
Next by Date: Re: [eclipse.org-architecture-council] Regrets
Previous by thread: [eclipse.org-architecture-council] JEP 336: deprecate pack200
Next by thread: [eclipse.org-architecture-council] Call Notes Posted - Next Meeting August 9
Index(es):
- Date
- Thread

Back to the top