github, restructuring and versioning

Stefan Negrea snegrea at redhat.com
Wed Mar 20 14:18:25 UTC 2013


Hello Jay,

Here is the BZ that tracks the work for the maven version changes: https://bugzilla.redhat.com/show_bug.cgi?id=923458  I suggest to have this BZ as a pre-requisite for the migration since it will be that much harder to address this after the migration.

For the Jenkins jobs, because the master versions of all the repositories will be in sync we do not really need additional jobs for plugins & helpers. We could just configure a few jobs to pull the plugin code along the core and build everything in one job. That way we keep the number of jobs low. We do not share artifacts across jobs so we would need to pull&build core for any separate plugins build even if there is a dedicated job.

Looking at the publishing plan, I only see publishing of core artifacts in the wiki. We currently publish everything, is there a plan to not publish plugins and helpers in the future?

Are you going to publish before migration the list of branches that will get migrated? The wiki does not currently have the list.


Thank you,
Stefan Negrea 

----- Original Message -----
> From: "Jay Shaughnessy" <jshaughn at redhat.com>
> To: rhq-devel at lists.fedorahosted.org
> Sent: Tuesday, March 19, 2013 1:49:13 PM
> Subject: Re: github, restructuring and versioning
> 
> 
> We'd like to move forward with the migration in the near future. The
> wiki [1] has been updated given the results of the various dev-list
> threads.  Please review the wiki and reply with any further concerns
> or
> questions.
> 
> [1] https://docs.jboss.org/author/display/RHQ/GitHub+migration
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
> 


More information about the rhq-devel mailing list