RE: [platform-releng-dev] How to manage patches in the CVS Repo?

[Kim Moir <Kim_Moir@xxxxxxxxxx>]

Some of the feature patches are built
by the developers themselves and versioned appropriately.  Some of
the patches are built by us using a small project on a test server.

To be honest, the process is painful.
 We would like to move away from the process of providing patched
features because there are issues with them.

It is much easier to just release the
changes into the appropriate map file branch and run a build.  Patched
features are useful if  want to release small surgical fixes but they
are maintenance issues.

Kim

"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx

07/04/2007 10:47 AM

Please respond to
"Eclipse platform release engineering list."        <platform-releng-dev@xxxxxxxxxxx>

To	"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
cc
Subject	RE: [platform-releng-dev] How to manage patches in the CVS Repo?

Thanks Kim -
 
I understand the concept of patched
features, but I'm wondering if and
where the feature patch is version
controlled and how it is actually built.
 
I can create a feature patch in
my workspace, and then add it to
the update site project -- it
will be built with a default qualifier e.g.
20070704. But this procedure is
not reproducable. I'd like my feature
patch to be checked in to CVS
somewhere, and labelled, perhaps
added to a mapfile and built in
a reproducable manner.
 
I was wondering how the Platform
Team has been managing this
in the past for the feature patches
that have been released to
the Platform Update Site?

Thanks,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm

 

---

From: platform-releng-dev-bounces@xxxxxxxxxxx
[mailto:platform-releng-dev-bounces@xxxxxxxxxxx] On Behalf Of Kim
Moir
Sent: Wednesday, July 04, 2007 4:09 PM
To: Eclipse platform release engineering list.
Subject: Re: [platform-releng-dev] How to manage patches in the CVS
Repo?


Hi Martin 

In the past, we have created patched features and ensure that the patched
feature adheres to the version numbering guidelines.

http://wiki.eclipse.org/Version_Numbering_Europa_Update
http://wiki.eclipse.org/Version_Numbering#Patch_features

See 
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tools/project_wizards/new_feature_patch.htm


Kim

"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx

07/02/2007 10:14 AM

Please respond to
"Eclipse platform release engineering list."        <platform-releng-dev@xxxxxxxxxxx>

To	"Eclipse platform release engineering list." <platform-releng-dev@xxxxxxxxxxx>
cc
Subject	[platform-releng-dev] How to manage patches in the CVS Repo?

Dear Platform Releng Team, 
  
For the DSDP-TM project, it looks like we'll have to prepare 
patches for two critical issues found just a bit too late. I've
seen such patches before on the Platform update site, and
I'm wondering how you are managing / version controlling
such patches. 
  
I haven't found anything the the /cvsroot/eclipse Repo or
on the Wiki. Are there any docs, any place I could go looking?
  
Thanks,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev