[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [p2-dev] How to handle fixes for 3.5.1?
|
Here is a rough "process":
- Create a new bug as clone of the original one
- Set the target milestone
- Get consent from component lead
- Attach the patch (note that the patch in the maintenance does not have to be the same one than in HEAD)
- Get patch reviewed
- Release
- Tag
I have captured that at http://wiki.eclipse.org/Equinox/p2/Maintenance_process
PaScaL
Henrik Lindberg ---08/03/2009 12:10:53 PM---Hi,
![]()
From: | ![]()
Henrik Lindberg <henrik.lindberg@xxxxxxxxxxxxxx> |
![]()
To: | ![]()
P2 developer discussions <p2-dev@xxxxxxxxxxx> |
![]()
Date: | ![]()
08/03/2009 12:10 PM |
![]()
Subject: | ![]()
[p2-dev] How to handle fixes for 3.5.1? |
Hi,
I fixed https://bugs.eclipse.org/bugs/show_bug.cgi?id=282079 which
should go into 3.5.1
It is now checked into HEAD.
Is there any documentation on procedure for getting things into
3.5.1 ? Additional reviewers? etc.
Henrik Lindberg
henrik.lindberg@xxxxxxxxxxxxxx
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev

