Henri Yandell wrote:
On 4/27/06, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
Henri Yandell wrote:
Given this positive feedback so far, I'm going to email the infra@
mailing list to see how they would go about doing it _if_ we decided
we wanted to move.

I think we should be moving from 1 project with 37 components to 37
projects - it'll allow us to manage the components individually of
each other without the kind of version overlap and general noise
issues that we currently have.
Jakarta Http Components just created their first Jira, and they got the
name JHCHTTPCORE. Thus this _could_ get caught up in a debate about
Jakarta and groupings.

That's the id-code rather than the name (afaik).

I didn't know that that was being standardised - JHCHTTPCORE is
terrible, sounds like a sneeze.

Ideally we should use whatever we want, it's not a namespace to fight
over, just need to be unique.

Henri,

I also find JHCHTTPCORE absolutely horrible. I chose this id as I thought it would be the most "politically correct" one. I would very much rather prefer HTTPCORE or JHTTPCORE. Do you envisage a particular Jira id naming convention for Jakarta projects? At this point it is still not too late for us to scrap the project and start over with a different (better) project id.

Oleg


Personally, I'd like to see each component able to move grouping within
Jakarta, thus we should use naming like JAKLANG or JAKARTALANG, rather
than JLCLANG (for Jakarta Language Components).

We also need to be aware that about half the commons websites now have
links tailored to bugzilla, and these links get placed into maven built
distributed projects. Another bit of work to do.

Not sure anything can be done about that one. Do you mean the sites
that get stuck in the zips (by maven built distributed projects) or
something else? I suspect that every project has had a period of cold
turkey when it moved over. Any idea Martin? Is there a .htaccess in
the Bugzilla somehow?

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to