pg.ddx.io  pgsql-pkg-docker@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Branches and versions
6+ messages / 3 participants
[nested] [flat]

* Branches and versions
@ 2014-07-14 23:19  Josh Berkus <josh@agliodbs.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Josh Berkus @ 2014-07-14 23:19 UTC (permalink / raw)
  To: pgsql-pkg-docker

All:

Currently there's one branch, REL9_3_4.  I'd like to change that.

Here's my thinking:

1) I'd like to backtrack to version 9.2.

2) I think we should only offer the current minor version of each
Postgres major version.  Therefore we'd have:

REL9_3 		(9.3.4)
REL9_2 		(9.2.8)
BETA9_4		(9.4b1)

Does this make sense?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


-- 
Sent via pgsql-pkg-docker mailing list (pgsql-pkg-docker@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-docker



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Branches and versions
@ 2014-07-15 15:47  Joseph Ferguson <joe@infosiftr.com>
  parent: Josh Berkus <josh@agliodbs.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Joseph Ferguson @ 2014-07-15 15:47 UTC (permalink / raw)
  To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-pkg-docker

On Mon, Jul 14, 2014 at 5:19 PM, Josh Berkus <josh@agliodbs.com> wrote:
> All:
>
> Currently there's one branch, REL9_3_4.  I'd like to change that.
>
> Here's my thinking:
>
> 1) I'd like to backtrack to version 9.2.
>
> 2) I think we should only offer the current minor version of each
> Postgres major version.  Therefore we'd have:
>
> REL9_3          (9.3.4)
> REL9_2          (9.2.8)
> BETA9_4         (9.4b1)
>
> Does this make sense?

Yes, this would be fairly simple and would also give us a chance to
drop the branch with all of the source.  Would it make more sense to
just delete the current docker-library/postgres repo and create a new
one with the same name (rather than just deleting the branch)?

- Joe Ferguson :: joe@infosiftr.com
  InfoSiftr :: Vice President of Programming


-- 
Sent via pgsql-pkg-docker mailing list (pgsql-pkg-docker@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-docker



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Branches and versions
@ 2014-07-15 15:55  Tianon Gravi <admwiggin@gmail.com>
  parent: Joseph Ferguson <joe@infosiftr.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Tianon Gravi @ 2014-07-15 15:55 UTC (permalink / raw)
  To: Joseph Ferguson <joe@infosiftr.com>; +Cc: Josh Berkus <josh@agliodbs.com>; pgsql-pkg-docker

On 15 July 2014 09:47, Joseph Ferguson <joe@infosiftr.com> wrote:
> Would it make more sense to
> just delete the current docker-library/postgres repo and create a new
> one with the same name (rather than just deleting the branch)?

Naw, it's so easy to delete a branch that we'd be silly not to just do that. :)

I think this will be easiest to track and update if we do it in
folders instead of branches (like Python[1]).

- Tianon

[1]: https://github.com/docker-library/docker-python


-- 
Sent via pgsql-pkg-docker mailing list (pgsql-pkg-docker@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-docker



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Branches and versions
@ 2014-07-16 20:17  Joseph Ferguson <joe@infosiftr.com>
  parent: Tianon Gravi <admwiggin@gmail.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Joseph Ferguson @ 2014-07-16 20:17 UTC (permalink / raw)
  To: pgsql-pkg-docker

On Tue, Jul 15, 2014 at 9:55 AM, Tianon Gravi <admwiggin@gmail.com> wrote:
>
> I think this will be easiest to track and update if we do it in
> folders instead of branches (like Python[1]).

We have set up a branch with each version in a folder[1].

Josh, what do you think?  Should we proceed with pushing this as the
official images?

[1] https://github.com/infosiftr/postgres/tree/docker

- Joe Ferguson :: joe@infosiftr.com
  InfoSiftr :: Vice President of Programming


-- 
Sent via pgsql-pkg-docker mailing list (pgsql-pkg-docker@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-docker



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Branches and versions
@ 2014-07-18 00:13  Josh Berkus <josh@agliodbs.com>
  parent: Joseph Ferguson <joe@infosiftr.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Josh Berkus @ 2014-07-18 00:13 UTC (permalink / raw)
  To: pgsql-pkg-docker

On 07/16/2014 01:17 PM, Joseph Ferguson wrote:
> On Tue, Jul 15, 2014 at 9:55 AM, Tianon Gravi <admwiggin@gmail.com> wrote:
>>
>> I think this will be easiest to track and update if we do it in
>> folders instead of branches (like Python[1]).
> 
> We have set up a branch with each version in a folder[1].
> 
> Josh, what do you think?  Should we proceed with pushing this as the
> official images?

That kind of structure seems unintuitive to me, as opposed to having
branches or tags.  What's the advantage?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


-- 
Sent via pgsql-pkg-docker mailing list (pgsql-pkg-docker@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-docker



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Branches and versions
@ 2014-07-18 00:30  Tianon Gravi <admwiggin@gmail.com>
  parent: Josh Berkus <josh@agliodbs.com>
  0 siblings, 0 replies; 6+ messages in thread

From: Tianon Gravi @ 2014-07-18 00:30 UTC (permalink / raw)
  To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-pkg-docker

On 17 July 2014 18:13, Josh Berkus <josh@agliodbs.com> wrote:
> That kind of structure seems unintuitive to me, as opposed to having
> branches or tags.  What's the advantage?

The advantage is that they're easier to manage and iterate on,
especially when you need to copy files between them (or compare
between them), which is something that in a case like this, we end up
doing quite often (in my experience).  Also, we're only going to have
two or three files each, so the management overhead of branches and
tags gets to be noticeable.

This also makes it a lot easier to work with and build two versions at
once, which is useful when you've just updated all the versions with
some new tweak and just need to build/test all of them.

- Tianon


-- 
Sent via pgsql-pkg-docker mailing list (pgsql-pkg-docker@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-docker



^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2014-07-18 00:30 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2014-07-14 23:19 Branches and versions Josh Berkus <josh@agliodbs.com>
2014-07-15 15:47 ` Joseph Ferguson <joe@infosiftr.com>
2014-07-15 15:55   ` Tianon Gravi <admwiggin@gmail.com>
2014-07-16 20:17     ` Joseph Ferguson <joe@infosiftr.com>
2014-07-18 00:13       ` Josh Berkus <josh@agliodbs.com>
2014-07-18 00:30         ` Tianon Gravi <admwiggin@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox