More Santuario infrastructure changes

[Colm O hEigeartaigh <co...@apache.org>]

Now that the Java 1.4.4 release is out the door, I want to revisit the
remaining infrastructure issues before work gets under way on a 1.5
release. Please let me know your opinion on the following tasks.

1) SVN tags

We have a large number of RC and beta tags in SVN:

http://svn.apache.org/viewvc/santuario/tags/

I suggest that we remove all *RC* and *beta* svn tags - apart from
Scott's recent RC for 1.6.0 :-)
This isn't a big deal if people object. It just cleans things up, and
makes the next point easier.

2) SVN reshuffle

We previously discussed this on private@. The consensus was to
separate out the Java and C projects.

 - trunk/c would move to xml-security-cpp/trunk. All c tags and
branches would move to xml-security-cpp/branches and
xml-security-cpp/tags.
 - Everything else under trunk would move to xml-security-java/trunk.
All Java tags and branches would move to xml-security-java/branches
and xml-security-java/tags.

3) Migrate from bugzilla to Jira

Jira is far easier to navigate and administer than bugzilla. Infra
told me they have tools to automate this process.

4) Move from gump to hudson for continuous integration

We currently use gump (at least in theory) to manage the Java build
and tests for continuous integration. Hudson
(https://hudson.apache.org/hudson/) is far superior and easier to use.

5) Move the website from forrest to a cwiki

We have an empty cwiki set up here - https://cwiki.apache.org/SANTUARIO/
Forrest is cumbersome and annoying. There will be an initial amount of
effort involved in the transition, but the website probably won't
change a huge amount after that.

Thoughts/opinions? Scott, do you want me to hold off on any of these
things until after a C 1.6.0 release? The first task is probably to do
the bugzilla -> JIRA migration.

Colm.

Re: More Santuario infrastructure changes

[Chad La Joie <la...@itumi.biz>]

That all sounds fine with me.

On 11/18/10 11:50 AM, Colm O hEigeartaigh wrote:
> Now that the Java 1.4.4 release is out the door, I want to revisit the
> remaining infrastructure issues before work gets under way on a 1.5
> release. Please let me know your opinion on the following tasks.
>
> 1) SVN tags
>
> We have a large number of RC and beta tags in SVN:
>
> http://svn.apache.org/viewvc/santuario/tags/
>
> I suggest that we remove all *RC* and *beta* svn tags - apart from
> Scott's recent RC for 1.6.0 :-)
> This isn't a big deal if people object. It just cleans things up, and
> makes the next point easier.
>
> 2) SVN reshuffle
>
> We previously discussed this on private@. The consensus was to
> separate out the Java and C projects.
>
>   - trunk/c would move to xml-security-cpp/trunk. All c tags and
> branches would move to xml-security-cpp/branches and
> xml-security-cpp/tags.
>   - Everything else under trunk would move to xml-security-java/trunk.
> All Java tags and branches would move to xml-security-java/branches
> and xml-security-java/tags.
>
> 3) Migrate from bugzilla to Jira
>
> Jira is far easier to navigate and administer than bugzilla. Infra
> told me they have tools to automate this process.
>
> 4) Move from gump to hudson for continuous integration
>
> We currently use gump (at least in theory) to manage the Java build
> and tests for continuous integration. Hudson
> (https://hudson.apache.org/hudson/) is far superior and easier to use.
>
> 5) Move the website from forrest to a cwiki
>
> We have an empty cwiki set up here - https://cwiki.apache.org/SANTUARIO/
> Forrest is cumbersome and annoying. There will be an initial amount of
> effort involved in the transition, but the website probably won't
> change a huge amount after that.
>
> Thoughts/opinions? Scott, do you want me to hold off on any of these
> things until after a C 1.6.0 release? The first task is probably to do
> the bugzilla ->  JIRA migration.
>
> Colm.
>

-- 
Chad La Joie
http://itumi.biz
trusted identities, delivered

Re: More Santuario infrastructure changes

[Colm O hEigeartaigh <co...@apache.org>]

I logged a JIRA to migrate the project from bugzilla:

https://issues.apache.org/jira/browse/INFRA-3212

Colm.

On Thu, Nov 18, 2010 at 5:28 PM, Scott Cantor <ca...@osu.edu> wrote:
>> 5) Move the website from forrest to a cwiki
>>
>> We have an empty cwiki set up here - https://cwiki.apache.org/SANTUARIO/
>> Forrest is cumbersome and annoying. There will be an initial amount of
>> effort involved in the transition, but the website probably won't
>> change a huge amount after that.
>
> We may have to do something here regarding the branding emails they sent
> out, but I didn't really understand yet what the emails were asking us to
> do.
>
>> Thoughts/opinions? Scott, do you want me to hold off on any of these
>> things until after a C 1.6.0 release? The first task is probably to do
>> the bugzilla -> JIRA migration.
>
> Let's hold off the svn change until then, it should be fairly soon, probably
> once I can get a Red Hat 6 image. The rest doesn't need to wait. I've closed
> most of the outstanding bugzilla issues, so I think I'm ok there.
>
> -- Scott
>
>
>

RE: More Santuario infrastructure changes

[Scott Cantor <ca...@osu.edu>]

> 5) Move the website from forrest to a cwiki
> 
> We have an empty cwiki set up here - https://cwiki.apache.org/SANTUARIO/
> Forrest is cumbersome and annoying. There will be an initial amount of
> effort involved in the transition, but the website probably won't
> change a huge amount after that.

We may have to do something here regarding the branding emails they sent
out, but I didn't really understand yet what the emails were asking us to
do.

> Thoughts/opinions? Scott, do you want me to hold off on any of these
> things until after a C 1.6.0 release? The first task is probably to do
> the bugzilla -> JIRA migration.

Let's hold off the svn change until then, it should be fairly soon, probably
once I can get a Red Hat 6 image. The rest doesn't need to wait. I've closed
most of the outstanding bugzilla issues, so I think I'm ok there.

-- Scott

Re: More Santuario infrastructure changes

[Sean Mullan <se...@oracle.com>]

Everything seems fine to me as well.

--Sean

On 11/18/10 11:50 AM, Colm O hEigeartaigh wrote:
> Now that the Java 1.4.4 release is out the door, I want to revisit the
> remaining infrastructure issues before work gets under way on a 1.5
> release. Please let me know your opinion on the following tasks.
>
> 1) SVN tags
>
> We have a large number of RC and beta tags in SVN:
>
> http://svn.apache.org/viewvc/santuario/tags/
>
> I suggest that we remove all *RC* and *beta* svn tags - apart from
> Scott's recent RC for 1.6.0 :-)
> This isn't a big deal if people object. It just cleans things up, and
> makes the next point easier.
>
> 2) SVN reshuffle
>
> We previously discussed this on private@. The consensus was to
> separate out the Java and C projects.
>
>   - trunk/c would move to xml-security-cpp/trunk. All c tags and
> branches would move to xml-security-cpp/branches and
> xml-security-cpp/tags.
>   - Everything else under trunk would move to xml-security-java/trunk.
> All Java tags and branches would move to xml-security-java/branches
> and xml-security-java/tags.
>
> 3) Migrate from bugzilla to Jira
>
> Jira is far easier to navigate and administer than bugzilla. Infra
> told me they have tools to automate this process.
>
> 4) Move from gump to hudson for continuous integration
>
> We currently use gump (at least in theory) to manage the Java build
> and tests for continuous integration. Hudson
> (https://hudson.apache.org/hudson/) is far superior and easier to use.
>
> 5) Move the website from forrest to a cwiki
>
> We have an empty cwiki set up here - https://cwiki.apache.org/SANTUARIO/
> Forrest is cumbersome and annoying. There will be an initial amount of
> effort involved in the transition, but the website probably won't
> change a huge amount after that.
>
> Thoughts/opinions? Scott, do you want me to hold off on any of these
> things until after a C 1.6.0 release? The first task is probably to do
> the bugzilla ->  JIRA migration.
>
> Colm.