In the thread with the epilogue, I went into how the epilogue could be, if well rendered, told without being told through the story its, rendering the strong suggestion that the epilogue would happen anyway. Epilogues, after all, contain a different direction, and that's not quite the same as a resolution. If it is, I would just make that my last chapter, not label it as an Epilogue.
That being said, the same is true in reverse. While I think it is useful to write a prologue that has, as for the epilogue, a different direction than the main novel, for purely notes purposes, true prologues I usually skip over when reading. Many times, however, people make Chapter 1, because it is from a different point of view or in a different place into their prologue, INTO their prologue by slapping that title on it. However, you can easily just make your "prologue" into Chapter 1 if it is pertinent to the main story arc of your novel. For instance, Eragon's prologue could have been Chapter 1, and thus I don't skip it when reading. However, this loose relation (not instant gratification like in Harry Potter's chapter 1-2 relationship, where we are left with harry then immediately return to him) could render it either way, and for that reason I would say it is likely that he made named the first section the Prologue, or Prelude, as it were. Both Harry Potter and Eragon's first sections, however, are set in a different time and from a different point of view. They are bound up in the main story arc so intimately, however, that personally I'd side with calling each "Chapter 1" as Rowling did for her story.
Touching on the true prologue, however, where there is a different aim than the main story arc, but nonetheless contributes to it, I would personally leave it for my note pile, but still make it. It would then be my task to render that section useless through weaving it through the story. My preference for leaving it in would most likely only be in the case of unlabeled prologues, like songs or short pieces of background that strike you and beg the question "why is this here?", acting as a hook for the story, which indeed includes, in its own manner, all the subtleties of the "prologue", which was brief and intriguing- worth the reader's time because it was short and pertinent in the broad sense of the story. As for weaving the prologue IN, even if it isn't present, you take both theme and substance and work in the necessity for the prologue being there into your story, enhancing it in the process. If the prologue is mostly for background, have the reader discover that as they go. If it is a sub-plot's inciting incident, have the sub-plot in the story, and have it be guided by that initial point, revealing what you want when you want to. This idea follows for many purposes that prologues might serve.
However, if you want suspence (though I believe there are better ways of doing this), you can potentially use the prologue to do so, though in this case I don't think you even need a prologue- like I said before: make it chapter 1.
Good luck!
