cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: cordova-plugins repo release
Date Thu, 28 Nov 2013 04:32:56 GMT
Back to the original question - we should specify how cordova-plugins
should be included in plugin releases.

Really, the thing we need is to be able to know if there are any unreleased
commits and to update releasenotes.md for each plugin.

I think it'd be enough to run "git log -- plugin-dir" and look for a
"Updated version to x.x.x" commit.

Do we need tags at all?


On Mon, Nov 25, 2013 at 6:32 PM, Brian LeRoux <b@brian.io> wrote:

> the problem wasn't isolated to the repo (there were many problems) but
> suffice to say lack of shared issue tracking was a key point of failure and
> inability to discreetly version changesets created more suffering than good
>
>
> On Mon, Nov 25, 2013 at 3:20 PM, Josh Soref <jsoref@blackberry.com> wrote:
>
> > Lindsey Simon wrote:
> > > It seems like a shared repo is just a recipe for the troubles of the
> last
> > > shared repo.
> >
> > For those of us who didn't live through the last shared repo, is there a
> > document describing what happened?
> >
> > There's a great writeup from some Github using group who accidentally
> > force pushed over a few hundred repositories :).
> >
> > ---------------------------------------------------------------------
> > This transmission (including any attachments) may contain confidential
> > information, privileged material (including material protected by the
> > solicitor-client or other applicable privileges), or constitute
> non-public
> > information. Any use of this information by anyone other than the
> intended
> > recipient is prohibited. If you have received this transmission in error,
> > please immediately reply to the sender and delete this information from
> > your system. Use, dissemination, distribution, or reproduction of this
> > transmission by unintended recipients is not authorized and may be
> unlawful.
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message