[
https://jira.jboss.org/jira/browse/DNA-580?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-580:
-----------------------------------
We already have acquired all the resources for the new name:
- we have a Magnolia project for the ModeShape
JBoss.org site
(
http://www.jboss.org/modeshape), though it's not yet active as I haven't
published it yet
- we own the 'modeshape.org' domain is ours, and
http://www.modeshape.org will
soon redirect to
http://www.jboss.org/modeshape, and we'll be able to use
'org.modeshape' for our package names.
- we have a new JIRA, and I will be moving all of the DNA issues into the ModeShape JIRA.
Our issues will be of the form "MODE-XYZ"
plus a new SVN repository, new mailing lists, new blog site, new Twitter account, and new
Ohloh project.
- we have a new logo design and should soon have the images we need
Here are the first steps:
1) The JBoss DNA SVN has already been locked down, and no more changes can be made to it.
DONE!
2) All of the history from the DNA SVN has already been loaded into the ModeShape SVN.
Basically, it looks exactly like the DNA repository did right after the 0.7 release. But
at the moment, it is locked down as well, pending the next step. DONE!
3) I will move all DNA JIRAs (all of them, including those that are complete or
incomplete) to the ModeShape JIRA. Any links to DNA issues will automatically redirect to
the corresponding issue in the ModeShape JIRA. The numbers won't match, but JIRA has
it's own way of doing things.
4) I've started renaming the projects, packages and classes. The projects will go
from 'dna-...' to 'modeshape-...", and our package structure will go from
"org.jboss.dna..." to "org.modeshape...". And any class that has
"DNA" in the name will be renamed. I will then commit these changes to the
ModeShape SVN. I will also move all of the JIRA issues from DNA to
5) I will then open up the ModeShape SVN, and you could switch your development
environments over to use
https://svn.jboss.org/repos/modeshape/trunk . But at this point,
we still only want to change JavaDoc, comments, and the documents.
After this is done, we'll release ModeShape 1.0.0.Beta1, which will essentially be the
same thing as DNA 0.7 except with the new brand, new module names, and updated
documentation. We'll publish the
http://jboss.org/modeshape project, and we'll
start publicizing everywhere we can. And, the code in SVN will be changed to be
1.0.0.GA-SNAPSHOT, and we can continue fixing issues, completing any part of the
rebranding, and working towards 100% TCK runs and 1.0.0.GA!
What can you do now?
- Sign up for the new mailing lists at
https://lists.jboss.org/mailman/listinfo/. As
usual, we have modeshape-announce@..., modeshape-commits@..., modeshape-dev@...,
modeshape-issues@..., and modeshape-users@....
- If you're on Twitter, follow @modeshape and retweet when the time comes
- If you use an RSS reader, add our new blog at
http://modeshape.wordpress.com/. No need
to do anything if you're already subscribed to the JBoss Feed.
- If you have any local changes, create some patches and edit them so that they'll
work with the new project names and package structure
- Go to the new IRC room, #modeshape on
freenode.net
- Relax for a few days while I do my magic with JIRA and SVN
Rebrand project to new name
---------------------------
Key: DNA-580
URL:
https://jira.jboss.org/jira/browse/DNA-580
Project: DNA
Issue Type: Task
Components: Analysis and Reporting, API, Common, Connectors, Development
Environment, Documentation, Examples, Federation, Graph, JCR, Maven Classloader, Query,
Search, Sequencers, Server, Testing, Tools, Views, Web Application
Affects Versions: 0.7
Reporter: Randall Hauch
Assignee: Randall Hauch
Priority: Blocker
Fix For: 1.0
The project will be rebranded, so we need to change the package names and all references
to "JBoss DNA" in the code and documentation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira