Re: [orbit-dev] Going once? Going twice?

[David M Williams <david_williams@xxxxxxxxxx>]

By all means. I hate to assume you are
volunteering, so will just ask,, who's to coordinate this, put some policy/mechanism
in place, be the one to track it, to nag anyone who's late, and then, when
they've determined all the proper sign-offs are done, flip the switch to
copy and declare the build? Chances are this is not a lot of work, so,
I'm sure someone (not me) would be willing to do it. 

BTW, sort of related, the CruiseControl
system we are using can notify anyone who contributes to a build, that
the build is done (that they contributed to). This produces a little less
spam, since anyone who does not contribute to a particular build, would
not be notificed. Anyone interested in enabling this sort of user-specifc
notification? To enable it, we'd (mostly) just have to put committers userIds
and email addresses in the CVSROOT/users file. (we do this in WTP). 

One more comment, in another note, Jeff
mentioned " we don't have any test suites", but .... there's
no reason we couldn't have some simple sanity checks. I've opened 
a "helpwanted" enhancement,
bug 173586, https://bugs.eclipse.org/bugs/show_bug.cgi?id=173586, if anyone
wants to comment (or, volunteer :)

Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx

02/08/2007 10:36 PM

Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

To	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
cc	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>, orbit-dev-bounces@xxxxxxxxxxx
Subject	Re: [orbit-dev] Going once? Going twice?

My motivations: it would make sure that contributors have validated the
content they put in and we avoid situations where the bundles produced
are not usable by the project maintaining it.  It also helps to remind
the different timelines (since committers will have to work at  M
-1, M +x) and also ensure that nobody forget the code they put in Orbit.

PaScaL

David M Williams <david_williams@xxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx

02/08/2007 08:36 PM

Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

To	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
cc
Subject	Re: [orbit-dev] Going once? Going twice?

Not sure, sounds like process to me and I am wondering what that process
would improve for our project. Is it a concern we declare too early when
some are not ready? Is it hoped to help remind people of their responsibilities
as they sign the dotted line?  I am sincerely interested in your thinking
here. Other options/opinons are quite welcome and I'd be happy to live
with the groups decision.

Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx

02/08/2007 07:19 PM

Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

To	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
cc	orbit-dev@xxxxxxxxxxx, orbit-dev-bounces@xxxxxxxxxxx
Subject	Re: [orbit-dev] Going once? Going twice?

Before declaring stability, I think we should have a sign off from all
the committers who have contributed a bundle (this way we will feel more
like a real project <g>). What do you think?

David M Williams <david_williams@xxxxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx

02/08/2007 06:45 PM

Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

To	orbit-dev@xxxxxxxxxxx
cc
Subject	[orbit-dev] Going once? Going twice?

Thanks everyone for some last minute reviews and fixes today. 

Unless I hear otherwise in the next few minutes, I'll copy this  build
in committers area 

http://download.eclipse.org/tools/orbit/committers/drops/S200702082257/

to the downloads area, and we'll declare Success, er, I mean Stable.

I think we can just leave the directory and zip file "dated",
instead of  renaming to "M1", unless 
anyone objects. I know this may seem odd, but Orbit is kind of an odd project
:) 
That is, doesn't have quite the fanfare associated with milestones, and
it's 
milestone intervals are fairly arbitrary. 

Thanks again, _______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev