On Tue, Jan 22, 2013 at 1:11 PM, Jody Garnett <[email protected]>wrote:
> The issue here is that the deploy to sourceforge failed so the server
> never tagged and pushed locally. Although there is an intermediate release
> branch. And indeed there are two. One for M0 and one for beta1. Which one
> was intended?
>
> Both! 9.0-M0 was "released" some months ago, 9.0-beta1 was released
> yesterday.
>
> Can you sneak into those directories and tag by hand?
>
Well I see the 9.0-beta1 tag but seems to be referring to a revision that
is not the exact one created by the release. I'll delete it and push up the
one on the build server, along with the 9.0-M0 tag which at this point
doesn't exist.
> Regarding the sourceforge upload we could make it so that it doesn't cause
> the script to fail (so it can continue on with the tag) but then we need to
> add a manual step to check that the artifacts were indeed uploaded.
>
> Or can curl check http HEAD ?
>
Yeah maybe. For now let's just create the directory.
>
> Jody
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
