User:Floratos - Revision history

Floratos at 06:59, 14 July 2013

2013-07-14T06:59:16Z

2013-07-14T06:58:56Z

2013-07-12T21:03:09Z

2006-02-21T06:02:59Z

‎Collaborative Development

2006-02-21T05:55:30Z

‎Collaborative Development

2006-02-21T05:53:14Z

2006-02-14T21:37:12Z

2006-02-14T21:34:50Z

2006-02-10T18:09:28Z

2006-02-03T16:48:33Z

‎Release Check List

← Older revision		Revision as of 06:59, 14 July 2013
Line 1:		Line 1:
	{{ArisTopNav}}		{{ArisTopNav}}
−
−	~~<sgallery>~~
−	~~LINCS_fMoA_Network_Zoom.png~~
−	~~LINCS_Functional_Mode_of_Action_Selector.png~~
−	~~LINCS_fMoA_Network_LinkOut_Entrez.png~~
−	~~</sgallery>~~

← Older revision		Revision as of 06:58, 14 July 2013
Line 1:		Line 1:
	{{ArisTopNav}}		{{ArisTopNav}}

−	~~{{Toggle\|Hi there!!!\|"show"}}~~	+	<sgallery>
		+	LINCS_fMoA_Network_Zoom.png
		+	LINCS_Functional_Mode_of_Action_Selector.png
		+	LINCS_fMoA_Network_LinkOut_Entrez.png
		+	</sgallery>

@@ Line 31: / Line 31: @@
 * An optional '''lib''' directory containing jar files required by the plugin.
-The application ant build script (which is made available to collaborative developers) will also create a '''classes''' directory which will contain the executable code. To create a new plugin called "example" a new directory with the same name will be created under the components module and CVS accounts will be issued to the members of the component development team. All developers in that team will become members of a new Unix group which will own the subdirectory (the rest of the world will have read-only rights). To
+The application ant build script (which is made available to collaborative developers) will also create a '''classes''' directory which will contain the executable code. To create a new plugin called "example" a new directory with the same name will be created under the components module and CVS accounts will be issued to the members of the component development team. All developers in that team will become members of a new Unix group which will own the subdirectory (the rest of the world will have read-only rights).
 ==Links from old "Developer" section==

@@ Line 31: / Line 31: @@
 * An optional '''lib''' directory containing jar files required by the plugin.
-The application ant build script (which is made available to collaborative developers) create also a '''classes''' directory which will contain the executable code. Developers of new plugins will be
+The application ant build script (which is made available to collaborative developers) will also create a '''classes''' directory which will contain the executable code. To create a new plugin called "example" a new directory with the same name will be created under the components module and CVS accounts will be issued to the members of the component development team. All developers in that team will become members of a new Unix group which will own the subdirectory (the rest of the world will have read-only rights). To
 ==Links from old "Developer" section==

@@ Line 23: / Line 23: @@
 ==Ken's tutorial==
 [[temp tutorial]]
 ==Links from old "Developer" section==

← Older revision		Revision as of 21:37, 14 February 2006
Line 1:		Line 1:
		+	{{ArisTopNav}}
		+
	==Release Check List==		==Release Check List==
	Here is a list of things we need to do/test before putting a new release on the site:		Here is a list of things we need to do/test before putting a new release on the site:

@@ Line 6: / Line 6: @@
 * Verify builds for all platforms by installing/running them in "virgin" environments.
 * Check that the technical documentation associated with each compoenent is up to date and that it has been versioned using the same version as the one of the component.
 ==Requirements To Consider==

← Older revision		Revision as of 18:09, 10 February 2006
Line 20:		Line 20:
	==Ken's tutorial==		==Ken's tutorial==
	[[temp tutorial]]		[[temp tutorial]]
		+
		+	==Links from old "Developer" section==
		+
		+	* [[Introduction_For_Developers\|Introduction For Developers]]
		+	* [[Devkit\|Instructions]] for the Developer Kit
		+	* [[Building geWorkbench]]
		+	* Coding Standards [[Style Guide]]
		+	* [http://caldev/workbench/api Javadocs]
		+	* [[CVS Repository]]
		+	* [[Screenshots]]
		+	* Information on [[.GEAR files]], a method of distributing plugins.
		+	* [[Plugin certification checklist]]

@@ Line 1: / Line 1: @@
 ==Release Check List==
 Here is a list of things we need to do/test before putting a new release on the site:
 * Check that the main menu option Help->Version lists the correct application and component versions.