Hello,

I am looking for comments on a proposal on how EDK II BaseTools is maintained.  
The goal is to move all tool related development activities to the EDK II 
BaseTools.  This is to address community feedback that there are long delays 
between changes made to the edk2-buildtools sub-project and the changes being 
propagated to EDK II BaseTools.  There has also been feedback that some 
developers do not want the overhead of pulling Win32 binaries when they are not 
required.  I am interested in your feedback (positive or negative) on this 
proposal and if you think steps should be added or removed or modified.

I would appreciate feedback by 7/18/2014.  Please let us know if you need more 
time to evaluate this proposal.

Proposed steps:
===============
1) Create new sub-project for BaseTools binaries 
        a. SVN Link: https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/
        b. Status: Done.
2) Intel to provide build server for BaseTools Win32 binaries
        a. SVN Link: 
https://svn.code.sf.net/p/edk2-toolbinaries/code/trunk/Win32/
        b. Build Frequency: Once per day, but only if there are source changes 
since last build.
        c. Build Time: 3 AM PDT
        d. Build server to send email with build log when build is performed.
        e. Build server send email that no build was required if no source 
changes since last build.
        f. Status: In progress.  Need a few more validation steps.
3) Delete Win32 binaries from EDK II BaseTools and replace with an SVN extern.
        a. Default will continue to pull Win32 binaries
        b. Developers that do not want Win32 binaries can opt-out by ignoring 
externs.
        c. Date: TBD.  Goal is immediately after build server is stable.
4) Merge sources from Edk2-buildtools to EDK II BaseTools
        a. Date: TBD.  Goal is immediately after build server is stable.
5) Change permissions on Edk2-buildtools sub-project to read-only and mark 
sub-project as inactive.
        a. Date: TBD.  Goal is immediately after EDK II BaseTools is synced 
with EDK2-buildtools.
6) Retire edk2-buildtools-comm...@lists.sourceforge.net mailing list.  All 
commits to BaseTools sources will show up on edk2-comm...@lists.sourceforge.net.
7) Retire edk2-buildtools-devel@lists.sourceforge.net and move all BaseTools 
related discussions to edk2-de...@lists.sourceforge.net 

Thanks,

Mike


------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
edk2-buildtools-devel mailing list
edk2-buildtools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-buildtools-devel

Reply via email to