Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Re: [eclipse.org-planning-council] RC1 Status? Please reply to the list with your status and bits

On the subject of RSS-based notification mechanisms, I could add a
callisto-related node or attribute (or a few?) to the feed's xml, such as
<build callisto="STAGING"/> or <update callisto="RELEASE"/> to store status
information.

If you have strong feelings one way or the other, please post comments
here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=116912#c22

or here:

http://wiki.eclipse.org/index.php/Eclipse_Build_Available_RSS_Feeds

or just send me a note. Please suggest what attributes/nodes you'd like to
see, and what suggested values for those attributes should be used to
identify status, like the 4 codes used for jar signing status.

Note that this code is making its way into org.eclipse.releng.basebuilder
soon. In the meantime, it exists as Ant tasks and scripts which can be
wired into whatever automated process exists for copying content from our
UM site to the Callisto staging site.

Cheers,

--
Nick Boldt :: Software Developer
Eclipse Modeling Framework :: http://eclipse.org/emf
IBM Toronto Lab, 8200 Warden Ave., D3/R8R/8200/MKM, Markham, L6G 1C7.
905/413/4308 || codeslave@xxxxxxxxxx && Nick Boldt/Toronto/IBM@IBMCA


Friday, April 21, 2006 6:02 AM
To: "eclipse.org-planning-council"
<eclipse.org-planning-council@xxxxxxxxxxx>
cc: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>,
eclipse.org-planning-council-bounces@xxxxxxxxxxx, Nick
Boldt/Toronto/IBM@IBMCA
From: Ed Merks/Toronto/IBM@IBMCA
Subject: Re: [eclipse.org-planning-council] RC1 Status? Please reply to the
list  with your status and bits


Bjorn,

For EMF.

   1. Yes.
   2. Done.
   3. None.
   4. Yes.
   5. No.  (David Williams has been doing this.  It needs to be automatable
      if we are to do it ourselves.)
   6. Yes.

We clearly need a more automated way of communicating all this kind
information, i.e., Nick's RSS feed idea for publishing build results which
also enables automatically kicking off downstream builds as dependencies
become available via their published build results.   He's making good
progress on this...


Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265  (t/l 969)



Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>




Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
04/20/2006 05:03 PM

                             Please respond to
                      "eclipse.org-planning-council"




                                                                         To
"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>,
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
                                                                         cc

                                                                    Subject
[eclipse.org-planning-council] RC1 Status? Please reply to the list
with your status and bits







Callisto People,
I'm confused about our status and I think probably other people are too so
could everyone send an email to the list with your RC1 status information:
   1. Have you finished your RC1 bits?
   2. If not, when do you expect to finish them?
   3. If you're waiting for another project, which one(s)?
   4. Have you placed those bits in your update site?
   5. Have you updated the features.xml file in the Callisto CVS directory?
   6. Are you ready for RC1 to be declared?
I know that some of you have already sent your status to the list, but if
you could do so again, that would be much appreciated.  Thank you.

I am out of town for the next week, so David Williams graciously agreed to
gather the information and potentially bug you if you haven't sent an email
to the list, etc.

Thanks,
Bjorn
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council




Back to the top