On Wed, 2005-10-05 at 23:53 -1000, Joshua Hoblitt wrote:
> I attempted to mechanize Pod generation from RT tickets this morning and
> ran into what I suspect is a bug in the RT client. Why don't we just
> commit BROKEN as is, make a note about it in RELEASE_INSTRUCTIONS, and
> plan on moving towa
On Wed, Oct 05, 2005 at 03:01:35PM -0700, chromatic wrote:
> On Mon, 2005-10-03 at 17:05 -1000, Joshua Hoblitt wrote:
>
> > I'm wondering if this wouldn't be better split up into RT tickets
> > similar to the way TODOs are handled. Having everything in one coherent
> > document is great but I sus
On Mon, 2005-10-03 at 17:05 -1000, Joshua Hoblitt wrote:
> I'm wondering if this wouldn't be better split up into RT tickets
> similar to the way TODOs are handled. Having everything in one coherent
> document is great but I suspect that significantly lowers the odds of
> the individual items bei
On Tue, Oct 04, 2005 at 06:30:05PM +0200, Leopold Toetsch wrote:
>
> There are 2 philosophies amongst people: some prefer RT, others prefer
> one document in the tree. The goal could be to auto-create BROKEN from
> RT tickets then. (I prefer one file, btw ;-)
That shouldn't be too hard with the
On Oct 4, 2005, at 5:05, Joshua Hoblitt wrote:
On Mon, Oct 03, 2005 at 06:17:30PM -0700, chromatic wrote:
I'll check this in in two days with regard to feedback from anyone
whose
opinion matters and what to call it and where to put it, if my initial
choice isn't perfect.
I'm wondering if
On Mon, 3 Oct 2005, Chromatic wrote:
> Here's (finally) a collection and summary of all of the known broken
> items in Parrot right now as a patch to create BROKEN.pod in the top
> level directory. If this isn't the right name or place to put the file,
> that's fine.
> +=item * Allow Building wi
On Mon, Oct 03, 2005 at 06:17:30PM -0700, chromatic wrote:
>
> I'll check this in in two days with regard to feedback from anyone whose
> opinion matters and what to call it and where to put it, if my initial
> choice isn't perfect.
I'm wondering if this wouldn't be better split up into RT ticket
Hi there,
Here's (finally) a collection and summary of all of the known broken
items in Parrot right now as a patch to create BROKEN.pod in the top
level directory. If this isn't the right name or place to put the file,
that's fine.
I'll check this in in two days with regard to feedback from any
