One more solution: On May 18, 2010, at 1:37 PM, Paul Trevithick wrote:
> Mike and Mary, > > With the of code from Azigo for the AIR active client now checked in we need > to create a plan for the formal release of Higgins 1.1. It has been a couple > years since we released Higgins 1.0 and I'm a bit rusty on all of what's > involved. Here are a few things that I can see at a glance that need doing: > > - Updating the Higgins 1.1 plan [1] page > - Creating a "Higgins 1.1RC" table here [2], including defining the > "solution" rows, and populating each cell. Currently (in 1.1M7) there are 11 > solutions defined. Each needs an owner, download link, solution level wiki > page, etc. as documented here [3]. > - Making sure all projects have the 1.1.XXX project version > - Making sure all code meets Eclipse guidelines (headers, copyright, EPL > license, etc) > - Scheduling with Eclipse for a formal release review > - Passing the release review > - Creating an SVN branch and tagging the build > - Updating the all build instruction pages for all "solutions" to reference > the correct branch/tag > - Resolving the OpenID4Java IP issues? > - Putting out a press release perhaps? Mary? > > Some details > > Looking at [2] we see 11 "solutions" listed under 1.1M7: > - GTK Selector 1.1-Win --move this to a "mothballed" section --the code is > "as is" but isn't formally part of 1.1 > - AIR Selector 1.1-Win --this solution page [4] needs to be updated to be > correct WRT to the new AIR code (architecture, build instructions, etc.. > - AIR Selector 1.1-Mac --as above > - Cloud Selector 1.1 --what is the status of this? Is it ready to go? > - iPhone Selector 1.1 --I think this is in pretty good shape > - STS IdP --update/dust off probably fine > - SAML IdP --update/dust off probably fine > - IdAS Solutions 1.1 --update/dust off probably fine > - IdAS Proxy Service 1.1 --move to a new Higgins 2.0 table (not used by H1.1 > code) > - XDI4J --update/dust off probably fine > - IdAS Attribute Service 1.1 --move to a new Higgins 2.0 table (not used by > H1.1 code) Hmm.. and it seems that our CardStore web service is a new and separate solution--so it needs its own solution-level wiki page. I realize that it is part of the I-Card Service and may not need separate build doc > > --Paul > > [1] http://wiki.eclipse.org/Higgins_1.1_Plan > [2] http://www.eclipse.org/higgins/downloads.php > [3] http://wiki.eclipse.org/Higgins_Committers_and_Contributors > [4] http://wiki.eclipse.org/AIR_Selector_1.1 >
_______________________________________________ higgins-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/higgins-dev
