[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
These look good. When the patches are ready add someone to the review list and we are good to go.
![Inactive hide details for Ian Bull ---04/30/2009 07:04:58 PM---Great week everyone! I really enjoyed being part of that and hel]()
Ian Bull ---04/30/2009 07:04:58 PM---Great week everyone! I really enjoyed being part of that and helping out where I could. From my testing today I think p2 has c
![]()
From: | ![]()
Ian Bull <irbull@xxxxxxxxxxxxxxxxx> |
![]()
To: | ![]()
P2 developer discussions <p2-dev@xxxxxxxxxxx> |
![]()
Date: | ![]()
04/30/2009 07:04 PM |
![]()
Subject: | ![]()
Re: [p2-dev] M7 and on |
Great week everyone! I really enjoyed being part of that and helping out where I could. From my testing today I think p2 has come together very nicely.
I have a few bugs that would be good to get in early in RC1. So when head opens up, can someone take a look at:
274612: [publisher] Category description not translated in site parser
https://bugs.eclipse.org/bugs/show_bug.cgi?id=274612
274467: [publisher] exporting for multiple platforms results in multiple entries in the eclipse.ini file
https://bugs.eclipse.org/bugs/show_bug.cgi?id=274467
261104: [publisher] Versioning Categories
https://bugs.eclipse.org/bugs/show_bug.cgi?id=261104
244421: [publisher] verify translations working with the publisher
https://bugs.eclipse.org/bugs/show_bug.cgi?id=244421
Cheers,
Ian
On Thu, Apr 30, 2009 at 2:54 PM, John Arthorne <John_Arthorne@xxxxxxxxxx> wrote:
The end-game rules take effect for any changes after M7, so essentially now. We usually do this by attaching a patch on the bug, and then asking another committer to look at it. A nice way to keep track of this is to set the "review" bugzilla flag to "?" and then enter the name of the committer to review. Then the commiter just has to switch the flag from "?" to "+" when they have reviewed it. This also makes it easy to query for all open bugs awaiting review. I think it will also be helpful for people to join #equinox-dev and we can ping people for reviews and discuss changes on there.
![]()
http://www.eclipse.org/eclipse/development/freeze_plan_3.5.php
John
Just to make sure I got this right:
Are you saying that the "only I builds mode, everything needs to be
reviewed" happens when RC1 milestone is reached, or is that in effect
now?
When in effect, is the review done with patches?
Henrik Lindberg
henrik.lindberg@xxxxxxxxxxxxxx
On Apr 30, 2009, at 11:19 PM, Pascal Rapicault wrote:
>
> Hello everyone,
>
> Even though M7 is not officially declared, I'm calling it done from
> the=
> p2
> standpoint as we have no outstanding issue left. Thank you for your
> efforts!
>
> Before entering the fix phase of RC1, I would like everyone to
> review t=
> heir
> assigned bugs marked 3.5 and decide if they should be addressed. At
> thi=
> s
> stage we should only be fixing things that are major hurdles and low
> ri=
> sk
> polish items, and as such we should not be shy of moving things out.
> If=
> you
> have any doubts or questions about a bug, ask the opinion of
> somebody e=
> lse
> on the team.
>
> Process wise, RC1 means that every fix must be reviewed by another
> contributor before being released (for this, please use the review
> entr=
> y in
> bugzilla). It also means no more N-build and just I-builds until the
> en=
> d of
> 3.5.
>
> Finally if no one has objection, once M7 will have been declared, I
> wil=
> l
> send out a call to the wider community asking for testing of their
> favourite scenarios and also proxy related issues that we don't have
> a =
> nice
> way of testing.
>
> PaScaL
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
