From: Farrukh Najmi <farrukh@wellfleetsoftware.com>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: ETA for release of gjit 0.4?
Date: Sat, 06 Dec 2008 13:57:00 -0500 [thread overview]
Message-ID: <493ACAFC.5040605@wellfleetsoftware.com> (raw)
In-Reply-To: <200812061947.27905.robin.rosenberg.lists@dewire.com>
Robin Rosenberg wrote:
> fredag 05 december 2008 15:34:36 skrev Farrukh Najmi:
>
>> Dear colleagues,
>>
>> I am using jgit in my maven project. Since current version is a SNAPSHOT
>> (0.4-SNAPSHOT) I cannot release my project with a SNAPSHOT dependency
>> (maven does not allow it). WHat is the time line for releasing version
>> 0.4 of jgit so I can plan accordingly.
>> Thanks for any info.
>>
>
> What? Plan? :)
>
:-)
> You could name the version something else like 0.3.1.42b27c
>
>
I could but maven (and good project release) practices are that a
project's release version should be managed by the project and not
consumers of the project.
BTW, If there is interest in maveninzing the project I can offer to
contribute that change to the project. Just let me know if that is
something the project wishes to do.
Maven offers many benefits to projects as described in links below. It
takes a little getting used to for project dev team but its not bad. It
does not impact consumers of projects negatively in any way.
Background blog:
<http://farrukhnajmi.blogspot.com/2008/02/why-maven-rocks-in-beginning-there-was.html>
More useful link:
<http://ebxmlrr.wiki.sourceforge.net/whymaven>
Thanks for a great project.
> It was a long time since we labeled anything. Shawn, how about merging
> my recent close-file-patches, reverting 3ffa47d9294086fbd1cdeb9b1564f922a23e3c6f
> and e7307f14c531d52cf231c39d844841c4adaf5e5a and then just call i 0.4 ?
>
> -- robin
>
> # from my pu branch, the latest Tentative build in the update site. Works quite well for
> me. Refactoring and
> $ git log --pretty=oneline origin/master..pu
> 2aafc054446f9b3aecdc01687a6949e4c54be6eb Revert "Rewrite GitMoveDeleteHook to use DirCacheBuilder"
> 439277860e1e315b7f0cd339b2435cc8311956c1 Revert "Teach GitMoveDeleteHook how to move a folder recursively"
> abc44bc6efa47c4c6e3c23f85fe9de9cd8460224 Improve closing of files in error situations.
> 22e2808ac2915446ed81115b663c684341ce6bdd Close a forgotten reference to the HEAD ref.
>
>
--
Regards,
Farrukh Najmi
Web: http://www.wellfleetsoftware.com
next prev parent reply other threads:[~2008-12-06 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 14:34 ETA for release of gjit 0.4? Farrukh Najmi
2008-12-06 18:47 ` Robin Rosenberg
2008-12-06 18:57 ` Farrukh Najmi [this message]
2008-12-08 16:21 ` Shawn O. Pearce
2008-12-08 16:35 ` Farrukh Najmi
2008-12-15 22:52 ` Farrukh Najmi
2008-12-16 3:56 ` Robin Rosenberg
2008-12-16 4:17 ` Robin Rosenberg
2008-12-16 4:23 ` Robin Rosenberg
2009-01-14 3:14 ` Jonas Fonseca
2008-12-08 16:52 ` Shawn O. Pearce
2008-12-08 17:13 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=493ACAFC.5040605@wellfleetsoftware.com \
--to=farrukh@wellfleetsoftware.com \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.com \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).