Jump to: navigation, search

Difference between revisions of "Hudson-ci/community meetings/nextAgenda"

(Minutes)
 
(5 intermediate revisions by one other user not shown)
Line 4: Line 4:
  
 
Add or comment on agenda items here, just prefix the item with your name so we can identify you on the call:  
 
Add or comment on agenda items here, just prefix the item with your name so we can identify you on the call:  
 +
*2.x?
 +
** [henrik]What is the status on the next release on the 2.x line?
  
 +
*3.0.0
 +
** [susan] M1 Release
 +
** [susan] Eclipse Move progress
 +
** [susan] Website and wiki
 +
** [susan] Initial Code Contribution
 +
** [susan] Issues migration
  
 +
* [manfred]Status on the Hudson book and strategy going forward
 +
** [henrik] Can the supporting images/icons be released from copyright restrictions? Enough so that if a OSS plugin book starts it can re-use some of the styling.
 +
 +
* [henrik] Status of eclipse gerrit rollout
 +
* [henrik] Status of new hudson-on hudson ? Mayby we should not move the actual hudson jobs,as I have most of them working already ready to load using the jobcreator tool
 +
* [henrik] Last time winston said he had "How to" for almost all extension points, can they be put online?
 +
* [henrik] What is our recommended plugin development going forward?
 +
** Do we recommend using @Extention or JSR330?
 +
** Are we moving away from Descriptor/Descripable and @DataBoundConstructor (stapler stuff)?
 +
** If we are is there any documentation on what the JSR330 replacements are ? (reading the sisu docs is not enough)
 +
*[henrik] Could we use something like : https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Compatibility+Tester. I think it would be a good idea, but I am not sure how much of the solution itself we can reuse. Personally I am not too fond of just downloading via a update centre, and it doesn't seem to support adding more tests in case the plugin provided ones are sub-standard.
 +
 +
= Minutes =
 +
 +
rough notes first!
 +
 +
Add or comment on agenda items here, just prefix the item with your name so we can identify you on the call:
 +
*2.x?
 +
** [henrik]What is the status on the next release on the 2.x line?
  
 
*3.0.0  
 
*3.0.0  
Line 13: Line 40:
 
** [susan] Initial Code Contribution  
 
** [susan] Initial Code Contribution  
 
** [susan] Issues migration  
 
** [susan] Issues migration  
** [henrik] Status of eclipse gerrit rollout
 
** [henrik] Status of hudson on hudson (new machine + hopefully I can report on some jobcreator progess)
 
 
  
 
* [manfred]Status on the Hudson book and strategy going forward  
 
* [manfred]Status on the Hudson book and strategy going forward  
* [henrik] Jason's suggestion for moving away from jira/confluence, my concerns are primarily:
+
** [henrik] Can the supporting images/icons be released from copyright restrictions? Enough so that if a OSS plugin book starts it can re-use some of the styling.
** The current confluence have alot of information that is cross cutting and not related to specific plugins, such as developer guides. Do you suggest we move all that to the eclipse wiki?
+
 
** What do we do about all the plugins which hasn't changed in a long time and thus still have a URL setting pointing to the hudson wiki?
+
* [henrik] Status of eclipse gerrit rollout - lucas send bug out
** We have pages that query the current state of a plugin such as the hudson-plugin-info macro would we loose this functionality or can the eclipse wiki provide the same?.
+
* [henrik] Status of new hudson-on hudson ? Mayby we should not move the actual hudson jobs,as I have most of them working already ready to load using the jobcreator tool - all but 3/4 cleared up plugins depending on snaps
** if we move shared content to the eclipse wiki, will eclipse introduce any restrictions in contributing or is it just as open as our current solution?
+
* [henrik] Last time winston said he had "How to" for almost all extension points, can they be put online? - winston to mail out.   winston will send them out.
 +
* [henrik] What is our recommended plugin development going forward?
 +
jsr330 (but latest tutorial not using it)
 +
** Do we recommend using @Extention or JSR330? for m2 - convert extension points to JSR330. then write and publish a plugin to encourage. if anyone already has notes, please let us know. (very little JSR330 doc) start with bundled plugins.
 +
how to migrate old style -
 +
how descriptor describle fits it
 +
** Are we moving away from Descriptor/Descripable ? winston, cannot get rid of descriptoo/describable as will break existing plugins and needed with Jelly
 +
** If we are is there any documentation on what the JSR330 replacements are ? (reading the sisu docs is not enough) - not much, hence winston will document for plugin developers.
 +
 
 +
*[henrik] Could we use something like : https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Compatibility+Tester. I think it would be a good idea, but I am not sure how much of the solution itself we can reuse. Personally I am not too fond of just downloading via a update centre, and it doesn't seem to support adding more tests in case the plugin provided ones are sub-standard.
 +
- we can write something that compiles from JSON against newer releases - winston and henrik to discuss and try it
 +
 
 +
eclipsecon - tutorial and session.
 +
- user stories and feedback would be good
 +
 
 +
mailing lists - why 2?
 +
cannot convert existing subscribers to eclipse - so would have to start from scratch.
 +
in eclipse - user forum, dev list - no user list - plugin developers - not eclipse.
 +
shall we change the uncaught exception message in hudson - to mail eclipse dev list - WINSTON to update
 +
do we need a plugin dev list outside eclipse? have one list is better. start making suggestion to dev to move to dev list.
 +
DECISION: more investigation and discuss in dev list
 +
java.net - user list - continue?
 +
 
 +
eclispelink/aspectj both have user and dev mailing lists. - can we? is there an archive for browsing.
 +
 
 +
svnkit - upgrade on fly is hard to accomplish - need to host SVN outside eclipse (github) and have users install it. M2 - winston to experiment on how best to achieve this? Geoff to log ER
 +
 
 +
if remove SVN - shall we remove git and CVS too? perhaps unbundle CVS completely if we are doing this. but many eclipse projects are still using CVS at the moment.
 +
 
 +
same with maven2 - on first install rather than loading additional plugins that are not used.
 +
 
 +
on upgrade - prompt to refresh too? winston to investigate if this is more problematic once a Hudson home is present.
 +
 
 +
update center - although maven2 is turned off - still asked if want to upgrade -(cos bundled) - another annoyance solved if external.
  
= Minutes =
 
  
''To Follow''
+
Susan Duncan
 +
Geoff Waymark
 +
Stuart McCulloch
 +
Henrik
 +
Brian Fry
 +
Lucas Panjer
 +
Winston Prakash

Latest revision as of 12:59, 6 February 2012

Hudson Continuous Integration Server
Website
Download
Community
Mailing ListForumsIRC
Bugzilla
Open
Help Wanted
Bug Day
Contribute
Browse Source
Hudson-bust.png Community Meeting 6-Feb-2012











Agenda

Add or comment on agenda items here, just prefix the item with your name so we can identify you on the call:

  • 2.x?
    • [henrik]What is the status on the next release on the 2.x line?
  • 3.0.0
    • [susan] M1 Release
    • [susan] Eclipse Move progress
    • [susan] Website and wiki
    • [susan] Initial Code Contribution
    • [susan] Issues migration
  • [manfred]Status on the Hudson book and strategy going forward
    • [henrik] Can the supporting images/icons be released from copyright restrictions? Enough so that if a OSS plugin book starts it can re-use some of the styling.
  • [henrik] Status of eclipse gerrit rollout
  • [henrik] Status of new hudson-on hudson ? Mayby we should not move the actual hudson jobs,as I have most of them working already ready to load using the jobcreator tool
  • [henrik] Last time winston said he had "How to" for almost all extension points, can they be put online?
  • [henrik] What is our recommended plugin development going forward?
    • Do we recommend using @Extention or JSR330?
    • Are we moving away from Descriptor/Descripable and @DataBoundConstructor (stapler stuff)?
    • If we are is there any documentation on what the JSR330 replacements are ? (reading the sisu docs is not enough)
  • [henrik] Could we use something like : https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Compatibility+Tester. I think it would be a good idea, but I am not sure how much of the solution itself we can reuse. Personally I am not too fond of just downloading via a update centre, and it doesn't seem to support adding more tests in case the plugin provided ones are sub-standard.

Minutes

rough notes first!

Add or comment on agenda items here, just prefix the item with your name so we can identify you on the call:

  • 2.x?
    • [henrik]What is the status on the next release on the 2.x line?
  • 3.0.0
    • [susan] M1 Release
    • [susan] Eclipse Move progress
    • [susan] Website and wiki
    • [susan] Initial Code Contribution
    • [susan] Issues migration
  • [manfred]Status on the Hudson book and strategy going forward
    • [henrik] Can the supporting images/icons be released from copyright restrictions? Enough so that if a OSS plugin book starts it can re-use some of the styling.
  • [henrik] Status of eclipse gerrit rollout - lucas send bug out
  • [henrik] Status of new hudson-on hudson ? Mayby we should not move the actual hudson jobs,as I have most of them working already ready to load using the jobcreator tool - all but 3/4 cleared up plugins depending on snaps
  • [henrik] Last time winston said he had "How to" for almost all extension points, can they be put online? - winston to mail out. winston will send them out.
  • [henrik] What is our recommended plugin development going forward?

jsr330 (but latest tutorial not using it)

    • Do we recommend using @Extention or JSR330? for m2 - convert extension points to JSR330. then write and publish a plugin to encourage. if anyone already has notes, please let us know. (very little JSR330 doc) start with bundled plugins.

how to migrate old style - how descriptor describle fits it

    • Are we moving away from Descriptor/Descripable ? winston, cannot get rid of descriptoo/describable as will break existing plugins and needed with Jelly
    • If we are is there any documentation on what the JSR330 replacements are ? (reading the sisu docs is not enough) - not much, hence winston will document for plugin developers.
  • [henrik] Could we use something like : https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Compatibility+Tester. I think it would be a good idea, but I am not sure how much of the solution itself we can reuse. Personally I am not too fond of just downloading via a update centre, and it doesn't seem to support adding more tests in case the plugin provided ones are sub-standard.

- we can write something that compiles from JSON against newer releases - winston and henrik to discuss and try it

eclipsecon - tutorial and session. - user stories and feedback would be good

mailing lists - why 2? cannot convert existing subscribers to eclipse - so would have to start from scratch. in eclipse - user forum, dev list - no user list - plugin developers - not eclipse. shall we change the uncaught exception message in hudson - to mail eclipse dev list - WINSTON to update do we need a plugin dev list outside eclipse? have one list is better. start making suggestion to dev to move to dev list. DECISION: more investigation and discuss in dev list java.net - user list - continue?

eclispelink/aspectj both have user and dev mailing lists. - can we? is there an archive for browsing.

svnkit - upgrade on fly is hard to accomplish - need to host SVN outside eclipse (github) and have users install it. M2 - winston to experiment on how best to achieve this? Geoff to log ER

if remove SVN - shall we remove git and CVS too? perhaps unbundle CVS completely if we are doing this. but many eclipse projects are still using CVS at the moment.

same with maven2 - on first install rather than loading additional plugins that are not used.

on upgrade - prompt to refresh too? winston to investigate if this is more problematic once a Hudson home is present.

update center - although maven2 is turned off - still asked if want to upgrade -(cos bundled) - another annoyance solved if external.


Susan Duncan Geoff Waymark Stuart McCulloch Henrik Brian Fry Lucas Panjer Winston Prakash