You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Andrew McIntyre <mc...@gmail.com> on 2005/03/26 01:35:23 UTC

snapshots posted on the website (was Re: Adding framework scripts to bundle)

On Thu, 24 Mar 2005 10:23:07 -0800, Satheesh Bandaram
<sa...@sourcery.org> wrote:
> I also think they are useful. Some of these scripts are present in the
> derby source download, though they could be improved. It would be nice
> to be able to start Derby Network server as a service in Windows, for
> example. Any volunteers? :-)

Actually, I've been planning on putting together an updated snapshot
for a couple of weeks now, one that includes the frameworks scripts
and the demos as well. Also, once I've had a chance to check in the
recent fix for the Eclipse plugin, the Eclipse plugin that is
currently posted should probably be updated as well. So, it seems
there is good reason all around to update the snapshots we have
available on the web.

But, see also here: 

http://mail-archives.eu.apache.org/mod_mbox/db-derby-dev/200502.mbox/%3c421CFA7C.4070500@Golux.Com%3e
and here:
http://mail-archives.eu.apache.org/mod_mbox/db-derby-dev/200502.mbox/%3c421F1D56.8000302@sbcglobal.net%3e

So maybe we should be putting a little more thought into what goes
into these snapshots. Perhaps we should be bumping the fourth part of
the version after each bug fix that goes in. Does that mean that we
need to go through the full release process each time? Or, since we
know that there has been such small, well-known sets of changes going
into the branches, is it maybe possible to do a more lightweight
release process for these small bug fix releases? It would require a
little more effort in documenting the changes and keeping the related
documentation in the branch (CHANGES, etc.) up to date, but it's worth
the effort, and I would be willing to help out with that.

Anyway, I'm planning on merging the demo changes from the trunk over
to the branch shortly and I would also like to get a new snapshot
posted and I will be glad to help out with whatever work is involved
to do that. But, I'm not sure that we should just throw another
snapshot up on the website. There are clearly some issues with
versioning and being able to differentiate between snapshots that
should be discussed, so if anyone has any comments, concerns, or
suggestions about a better process for posting snapshots to the
website, please post them.

Thanks,
andrew