[brailleblaster] Re: push by john.bo...@xxxxxxxxxxxxxxxxx - Adding indevelopment package for developing final semantics and style ... on 2012-10-24 19:15 GMT
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: brailleblaster@xxxxxxxxxxxxx
- Date: Wed, 24 Oct 2012 19:08:22 -0500
What do you suggest as an alternative package name? I want people to be
able to lok at this code, so they can see how BrailleBlaster will
eventually operate. Putting it in the default branch seemed like the
best way to make it available.
John
On Thu, Oct 25, 2012 at 12:10:10AM +0100, Michael Whapples wrote:
> Is this wise to call the package name indevelopment? I would not want
> the job of refactoring the code when its production ready, or is it
> never going to be used outside the package until its ready?
>
> As you sent a message to the list explaining for contents of the package
> not to be used until completed, is it really necessary to give it
> "meaningless" names which give no indication of the purpose of the
> package? If anything which is in development were to be placed in this
> package then unrelated things may get mixed together. Remember about
> javadoc, there is even a file for package information, note that code is
> development code in the javadoc.
>
> Also with distributed version control systems like mercurial, remember
> you can work in a local repository, committing there as much as you
> like, and only push to the central repository when you feel its ready
> for public consumption. Thus that also would get away from any concerns
> of people using code which is not ready.
>
> Michael Whapples
--
John J. Boyer; President, Chief Software Developer
Abilitiessoft, Inc.
http://www.abilitiessoft.com
Madison, Wisconsin USA
Developing software for people with disabilities
Other related posts:
