basically yes (using git push origin :refs/tags/TAG). But you're still left with
the problem of the additionl mvn release plugin commits. And those can only be
removed by using git reset --hard and git push origin +BRANCH which makes it
quite a dirty business...
kind regards
On Thu, Oct 28, 2010
Doesn't this do the job of removing a remote tag?
On Tue, Oct 26, 2010 at 10:46 AM, Guillaume Nodet wrote:
> You can always push manually once after having deployed, verified and
> promoted the repository.
> I don't think there's an easy way to delete a tag that has been
> pushed, so if anything
Great, this does the job :) can't we add this mail as is to the release
descriptions; or create a new page for upgrade to github/release at github. Only
difference: I've used developerConnection directly and set it with -D at runtime
as explained here [1]
thanks again and kind regards,
andreas
[1
You can always push manually once after having deployed, verified and
promoted the repository.
I don't think there's an easy way to delete a tag that has been
pushed, so if anything goes wrong, you need to force push, which is
kinda a bad idea afaik.
I've had to recut locally the release several ti
I'm not sure y we do not want to push the changes?
kind regards
On Mon, Oct 25, 2010 at 06:01:13PM +0200, Guillaume Nodet wrote:
>Actually, feel free to go ahead, pax-web does not really depend on
>pax-url, so it's not worth holding and pax-url has a new module based
>on aether which
1.0, 1.0.0, 1.0.0.RELEASE is IMHO a matter of personal taste, but I'm fine with
1.0 too :) should I push the pax-web version to 1.0? I think it is stable enough
for this step...
kind regards
On Tue, Oct 26, 2010 at 08:26:29AM +0800, Niclas Hedhman wrote:
> On Mon, Oct 25, 2010 at 11:20 AM, Andrea
On Mon, Oct 25, 2010 at 11:20 AM, Andreas Pieber wrote:
> [2] Describes the release process of ops4j proejcts. The following point's I'm
> not sure about:
>
> *) [2] makes difference between releases <1.0 and >=1.0 Is this really of
> relevance? IMHO all artifacts should be located at mvn central
Actually, feel free to go ahead, pax-web does not really depend on pax-url,
so it's not worth holding and pax-url has a new module based on aether which
seems to not be ready to be shipped.
I have some infos about releasing from github though.
Here is a patch I've used locally on org.ops4j.pax.ur
sounds great, thank you
On Mon, Oct 25, 2010 at 09:59:57AM +0200, Guillaume Nodet wrote:
>I'm doing it right now, so if there's no objection to release pax-url,
>I can cut a release today or tomorrow.
>
>On Mon, Oct 25, 2010 at 09:38, Andreas Pieber <[1]anpie...@gmail.com>
>wrote:
I'm doing it right now, so if there's no objection to release pax-url, I can
cut a release today or tomorrow.
On Mon, Oct 25, 2010 at 09:38, Andreas Pieber wrote:
> When do you like to implement the changes? I mean, after I've pushed the
> snapshots I can wait, but nevertheless I prefere minor f
When do you like to implement the changes? I mean, after I've pushed the
snapshots I can wait, but nevertheless I prefere minor frequent releases above
huge and rare ones. I've no problem cutting another release (pax-web-0.8.1) in
two or three weeks...
kind regards
On Mon, Oct 25, 2010 at 08:15:
On Mon, Oct 25, 2010 at 08:53:54AM +0300, Alin Dreghiciu wrote:
> hi,
>
> On Mon, Oct 25, 2010 at 6:20 AM, Andreas Pieber wrote:
> > hey,
> >
> > Its been a while since the last pax-web release and I think with the
> > upgrade to
> > jetty 7 it's time to do it again :) Nevertheless, it's my firs
On Mon, Oct 25, 2010 at 05:20, Andreas Pieber wrote:
> hey,
>
> Its been a while since the last pax-web release and I think with the
> upgrade to
> jetty 7 it's time to do it again :) Nevertheless, it's my first release of
> a pax
> project so I share my ideas with you; feel free to correct me :)
hi,
On Mon, Oct 25, 2010 at 6:20 AM, Andreas Pieber wrote:
> hey,
>
> Its been a while since the last pax-web release and I think with the upgrade
> to
> jetty 7 it's time to do it again :) Nevertheless, it's my first release of a
> pax
> project so I share my ideas with you; feel free to corre
hey,
Its been a while since the last pax-web release and I think with the upgrade to
jetty 7 it's time to do it again :) Nevertheless, it's my first release of a pax
project so I share my ideas with you; feel free to correct me :)
I've scanned the pax-web JIRA project for opened issues assigend t
15 matches
Mail list logo
