Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Reminders of "to-dos" this week


Denis

At what time will you be turning off synchronization for our projects so we can push up our release builds?

Kim





Eclipse WebMaster <webmaster@xxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

09/26/2006 09:48 PM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject
Re: [cross-project-issues-dev] Reminders of "to-dos" this week





Egad!

Yes, Kim is right; I had specifically asked that Platform, CDT and WTP
notify us webmasters in advance of releases (anything with an R- in
front of it) so we can allow mirrors to sync up. Nothing here has
changed. In fact, this applis perhaps even more so now if Platform, WTP
*and* CDT will be doing a maintenance release all on the same day.

Don't be fooled: a Platform maintenance release without any mirrors will
give everyone a good part of the day off as our site grinds to a
screeching halt.

Kim's (B) point below is also to be taken into consideration.

Thanks,

D.

Kim Moir wrote:
>
> Historically speaking, if I make a release available on eclipse.org
> without ensuring it can be downloaded from a few mirrors in advance...
>
> A. Eclipse.org's bandwidth becomes saturated because everyone is
> downloading or running updates from eclipse.org instead of a mirror
> B. Everyone complains that they can't download eclipse R x.x.x because
> it's not on a mirror yet
>
> So if this has changed, and I can just release eclipse 3.2.1  (complete
> zips & updates) at will, let me know.  I know this has caused problems
> in the past.
>
> Kim
>
>
>
>
> *David M Williams <david_williams@xxxxxxxxxx>*
> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
>
> 09/26/2006 04:37 PM
> Please respond to
> Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
>
>
>                  
> To
>                  Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
> cc
>                  
> Subject
>                  Re: [cross-project-issues-dev] Reminders of "to-dos" this week
>
>
>                  
>
>
>
>
>
>
> Yes, that's my understanding. (if I understand your question :)
>
> Sound ok? It is believed there is no massive downloads during
> maintenance releases, like there is for releases, so careful timing was
> not believed to be required.
>
> But ... I was so disappointed the release went so smoothly (without the
> yearly work stoppage waiting for Eclipse :) .... so perhaps we'll prove
> it only went smoothly with all that careful planning and timing?  :)
>
> If anyone "knows better" and thinks more care is needed here, please let
> us (and the webmasters!) know.
>
>
>
> *Kim Moir <Kim_Moir@xxxxxxxxxx>*
> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
>
> 09/26/2006 04:20 PM
> Please respond to
> Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
>
>                  
> To
>                  Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
> cc
>                  
> Subject
>                  Re: [cross-project-issues-dev] Reminders of "to-dos" this week
>
>
>
>                  
>
>
>
>
>
>
>
> Hi David
>
> To clarify, when you say there is no
> "take-offline-and-perform-a-mass-copy" do you mean that the eclipse
> foundation webmasters don't intend to stop the replication on the nodes
> to allow the releases to synchronize on the mirrors before they are
> visible on eclipse.org?
>
> Kim
>
>
> *David M Williams <david_williams@xxxxxxxxxx>*
> Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
>
> 09/25/2006 05:45 PM
> Please respond to
> Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
>
>
>                  
> To
>                  cross-project-issues-dev@xxxxxxxxxxx
> cc
>                  
> Subject
>                  [cross-project-issues-dev] Reminders of "to-dos" this week
>
>
>
>
>                  
>
>
>
>
>
>
>
>
> Just wanted to remind everyone of the tasks for the "Callisto Fall
> Maintenance" release.
>
> Final bits are due Wednesday, 27th, to allow mirror propagation time by
> Friday 9/29, the formal "release" of the maintenance release.
>
> There is no "take-offline-and-perform-a-mass-copy" as there was before,
> so I suggest updating and "deploying" as soon as possible,
> to avoid any last minute rush.
>
> Remember to update your own project update sites! Users who already have
> your features installed should be able to say "update existing
> features" and get the updates from your project site, not Callisto.
>
> The main purpose of updating the Callisto site is so that people
> "starting anew" will get the latest stuff, and not immediately have to
> get updates after they install.
>
> And, if I may speak for Bjorn :)
> don't forget there is a Planning Call on Thursday, the 28th, with an
> important agenda item.
>
>     * Thursday, September 28 9am PT, noon ET
>           o Go-no-go decision meeting
>       /613.287.8000 or 866.362.7064 passcode 874551#/
>
>
>       See
>       http://wiki.eclipse.org/index.php/Callisto_Coordinated_Maintenance
>       _______________________________________________
>       cross-project-issues-dev mailing list
>       cross-project-issues-dev@xxxxxxxxxxx
>       https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>       _______________________________________________
>       cross-project-issues-dev mailing list
>       cross-project-issues-dev@xxxxxxxxxxx
>       https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>       _______________________________________________
>       cross-project-issues-dev mailing list
>       cross-project-issues-dev@xxxxxxxxxxx
>       https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top