if releases/2020-12  depends on epp/packages/2020-12
shouldnt the epp/packages/2020-12 be created first then?

Am 15.09.20 um 14:40 schrieb Jonah Graham:
> Hi folks,
>
> When I took over the release process I was told that the next repo was
> to be created *after* the release and that is what is in my
> checklist: https://hackmd.io/@jonahgraham/eclipse-epp-release-process
> <https://hackmd.io/@jonahgraham/eclipse-epp-release-process>
>
> The different repos are handled by different people and I don't think
> we are going to coordinate more than we are already doing - i.e. I am
> fine of having a window when these new repos need to be made. If
> someone wants to coordinate across the multiple projects and choose a
> window please let me know. In the meantime I will be making the p2
> repo for 2020-12 tomorrow morning just after the release.
>
> Jonah
>
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com <http://www.kichwacoders.com>
>
>
> On Tue, 15 Sep 2020 at 08:15, Ed Merks <ed.me...@gmail.com
> <mailto:ed.me...@gmail.com>> wrote:
>
>     It's not a problem that it comes soon after, it's just more
>     convenient
>     (for me) for generating the catalog if it's (the train and the epp
>     repos) there significantly earlier.   Given they just compose the
>     previous release repos, they could be created at any time...
>
>     As Christian suggests, important that if the next train repo is there
>     that it be consistently there...
>
>     On 15.09.2020 11:41, Christian Dietrich wrote:
>     > for me the main thing to ask here is for consistency
>     >
>     > (if one is there, the other should be there too)
>     >
>     > Am 15.09.20 um 11:20 schrieb Frederic Gurr:
>     >> Hi,
>     >>
>     >> I think we should clarify when the "next-release" repos need to
>     be in
>     >> place to avoid unnecessary posts and emails every three months.
>     >>
>     >> Some time ago, the request for "next-release" repos came soon
>     after a
>     >> release dropped (usually at 10:01AM on a release Wednesday).
>     Now we are
>     >> down to Tuesday morning (SimRel and EPP) and Monday (Orbit)
>     before the
>     >> release is even out.
>     >>
>     >> FYI: I usually create the "next-release" SimRel repo on the
>     release day
>     >> (see also: https://wiki.eclipse.org/SimRel/Release_Checklist
>     <https://wiki.eclipse.org/SimRel/Release_Checklist>).
>     >>
>     >> Is it a major blocker if those three "next-release" repos are
>     not in
>     >> place before the official GA release? If yes, what is a
>     reasonable date
>     >> and time for them to be created?
>     >>
>     >>
>     >> Regards,
>     >>
>     >> Fred
>     >>
>     >>
>     >>
>     >> On 15.09.20 10:41, Ed Merks wrote:
>     >>> It would be great if both existed now so that I can generate
>     the catalog
>     >>> now, rather than regenerating it against soon after the
>     release when
>     >>> they are available.
>     >>>
>     >>> On 15.09.2020 10:31, Christian Dietrich wrote:
>     >>>> hi, it looks like download.eclipse.org/releases/2020-12
>     <http://download.eclipse.org/releases/2020-12> was created,
>     >>>> but download.eclipse.org/technology/epp/packages/2020-12
>     <http://download.eclipse.org/technology/epp/packages/2020-12> is still
>     >>>> missing*10:26:18* [ERROR] Failed to resolve target definition
>     >>>>
>     
> /home/jenkins/agent/workspace/ext-eclipse_cd_xtext_issuue1831b/releng/org.eclipse.xtext.target/org.eclipse.xtext.target-latest.target:
>     >>>> Failed to load p2 metadata repository from location
>     >>>> https://download.eclipse.org/releases/2020-12
>     <https://download.eclipse.org/releases/2020-12>: Unable to read
>     >>>> repository at https://download.eclipse.org/releases/2020-12
>     <https://download.eclipse.org/releases/2020-12>. No
>     >>>> repository found at
>     >>>> https://download.eclipse.org/technology/epp/packages/2020-12
>     <https://download.eclipse.org/technology/epp/packages/2020-12>. ->
>     [Help
>     >>>> 1] ~Christian
>     _______________________________________________
>     cross-project-issues-dev mailing list
>     cross-project-issues-dev@eclipse.org
>     <mailto:cross-project-issues-dev@eclipse.org>
>     To unsubscribe from this list, visit
>     https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>     <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev>
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to